Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dee604e41cc4f68e1b6573c80b03c0dd8bd721acd4008684e7d455aebfef2ee0

Tx prefix hash: b11e44793ccb44043e2650ae13417c86894a26a36c3e91e5799cdc40ef4d7457
Tx public key: bd999abe7fc4f5db51dd7a6e023e742832ee08605666a3a373e2a59218183181
Timestamp: 1717763120 Timestamp [UCT]: 2024-06-07 12:25:20 Age [y:d:h:m:s]: 00:327:11:22:16
Block: 1039015 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234039 RingCT/type: yes/0
Extra: 01bd999abe7fc4f5db51dd7a6e023e742832ee08605666a3a373e2a5921818318102110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c8da7b49eac254e62044ea66b031ba3037c2e2ad322a8df678af4c6c718b239 0.600000000000 1507598 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": 1039025, "vin": [ { "gen": { "height": 1039015 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c8da7b49eac254e62044ea66b031ba3037c2e2ad322a8df678af4c6c718b239" } } ], "extra": [ 1, 189, 153, 154, 190, 127, 196, 245, 219, 81, 221, 122, 110, 2, 62, 116, 40, 50, 238, 8, 96, 86, 102, 163, 163, 115, 226, 165, 146, 24, 24, 49, 129, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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