Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1fd2ce321b3dc7dbc7553308e56d54f41673f3d868436c2ba0edbbd4c46317e

Tx prefix hash: 2ddcfd975e31ad0f7ee70be857dbb252c8206ce79f91099b37b6aac88ce5afe8
Tx public key: 7ccd6ea5a81d5163a280d3b7bb47cfcc1f97541d86960939f676700413e3ea9f
Timestamp: 1713998279 Timestamp [UCT]: 2024-04-24 22:37:59 Age [y:d:h:m:s]: 00:350:12:28:35
Block: 1007797 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250579 RingCT/type: yes/0
Extra: 017ccd6ea5a81d5163a280d3b7bb47cfcc1f97541d86960939f676700413e3ea9f0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6126eb6c0246632744e8444c0b99a2e27bd1e33cf6323b2f19ebf02aef8829d 0.600000000000 1469251 of 15

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": 1007807, "vin": [ { "gen": { "height": 1007797 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6126eb6c0246632744e8444c0b99a2e27bd1e33cf6323b2f19ebf02aef8829d" } } ], "extra": [ 1, 124, 205, 110, 165, 168, 29, 81, 99, 162, 128, 211, 183, 187, 71, 207, 204, 31, 151, 84, 29, 134, 150, 9, 57, 246, 118, 112, 4, 19, 227, 234, 159, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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