Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: cf779a6519178e610294208cb5be080b9073ba8aba379927f2879cd9bb6c6708

Tx prefix hash: 70cbd27e3f9174d0760042b7ee930e078fe6c8b94d1128d6950871c6c1affbc0
Tx public key: cd52d3d4bac0fbf6146f115ffec7b076efdb534947269d42302d80bc34ecb4f2
Timestamp: 1643917480 Timestamp [UCT]: 2022-02-03 19:44:40 Age [y:d:h:m:s]: 02:287:02:59:22
Block: 431556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 723699 RingCT/type: yes/0
Extra: 01cd52d3d4bac0fbf6146f115ffec7b076efdb534947269d42302d80bc34ecb4f2021100000001a272b9cb000000000000000000

1 output(s) for total of 22.807418434000 dcy

stealth address amount amount idx
00: 1cafe6f5e193c0c329d3180c519ccbdac5298ad1bab8db974b563dc6f14d9c4c 22.807418434000 841809 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 431566, "vin": [ { "gen": { "height": 431556 } } ], "vout": [ { "amount": 22807418434, "target": { "key": "1cafe6f5e193c0c329d3180c519ccbdac5298ad1bab8db974b563dc6f14d9c4c" } } ], "extra": [ 1, 205, 82, 211, 212, 186, 192, 251, 246, 20, 111, 17, 95, 254, 199, 176, 118, 239, 219, 83, 73, 71, 38, 157, 66, 48, 45, 128, 188, 52, 236, 180, 242, 2, 17, 0, 0, 0, 1, 162, 114, 185, 203, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8