Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df47607a1cd8e1280698f009e1339ac8bfc616cc137954bf18d0c7fd3412fcac

Tx prefix hash: 21937073ef0c19e4edac361e0a47427b3ea70eb7cbfab1e118e2c981dcf4ec4a
Tx public key: d23f1794c0cf1e6bbf7861e2ee40950e0056f338b8c3e9fb67248172bfd9585e
Timestamp: 1703708641 Timestamp [UCT]: 2023-12-27 20:24:01 Age [y:d:h:m:s]: 01:111:15:36:32
Block: 922489 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340919 RingCT/type: yes/0
Extra: 01d23f1794c0cf1e6bbf7861e2ee40950e0056f338b8c3e9fb67248172bfd9585e021100000003ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae03b65c22b501854fd1d0c070ff3a54a8d3b0637ce3b2612da08e4ea86dcc88 0.600000000000 1380187 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": 922499, "vin": [ { "gen": { "height": 922489 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae03b65c22b501854fd1d0c070ff3a54a8d3b0637ce3b2612da08e4ea86dcc88" } } ], "extra": [ 1, 210, 63, 23, 148, 192, 207, 30, 107, 191, 120, 97, 226, 238, 64, 149, 14, 0, 86, 243, 56, 184, 195, 233, 251, 103, 36, 129, 114, 191, 217, 88, 94, 2, 17, 0, 0, 0, 3, 173, 86, 148, 172, 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