Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5ff5d9aed3567ccf9cf0b4d7473c0010633584cb63cbf8d8196259d8999be59

Tx prefix hash: 771e8b8fbe157cba2178b35cee3056650a1f0d2c14a575470a8c1fbc39f0ffbb
Tx public key: 56d949476b69676db3f38469932087c5df495f9ac8a2e8baaeab2deb10a18dde
Timestamp: 1640950245 Timestamp [UCT]: 2021-12-31 11:30:45 Age [y:d:h:m:s]: 02:362:01:01:47
Block: 407417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 776867 RingCT/type: yes/0
Extra: 0156d949476b69676db3f38469932087c5df495f9ac8a2e8baaeab2deb10a18dde021100000031ed5d3ead000000000000000000

1 output(s) for total of 27.419447069000 dcy

stealth address amount amount idx
00: 84d5c97d2b461e6d09bcb72b34fcbafadfe7be62e89e58eea04708de756c92a6 27.419447069000 808889 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": 407427, "vin": [ { "gen": { "height": 407417 } } ], "vout": [ { "amount": 27419447069, "target": { "key": "84d5c97d2b461e6d09bcb72b34fcbafadfe7be62e89e58eea04708de756c92a6" } } ], "extra": [ 1, 86, 217, 73, 71, 107, 105, 103, 109, 179, 243, 132, 105, 147, 32, 135, 197, 223, 73, 95, 154, 200, 162, 232, 186, 174, 171, 45, 235, 16, 161, 141, 222, 2, 17, 0, 0, 0, 49, 237, 93, 62, 173, 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