Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e4b60a16cc540f070c7ba3bab17b31352ac7437895fbd3eb02cb36f94fe235d

Tx prefix hash: bb7aa4af729006a05c3f635d933269ed23c7503b2bb5340036e7c86b57341218
Tx public key: 671efa8694ed08e6d3ffcbff3b4704726ea4fd65fbc3eb6334d1bfe727e59fbf
Timestamp: 1637692336 Timestamp [UCT]: 2021-11-23 18:32:16 Age [y:d:h:m:s]: 03:344:05:58:33
Block: 380575 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1022421 RingCT/type: yes/0
Extra: 01671efa8694ed08e6d3ffcbff3b4704726ea4fd65fbc3eb6334d1bfe727e59fbf021100000003e59f5d07000000000000000000

1 output(s) for total of 33.650957081000 dcy

stealth address amount amount idx
00: 5fb1d7af6b9dcf5f91ef15ead5ada2a947e4a47a385a7dc92a2ca3b6475c0e1a 33.650957081000 769041 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": 380585, "vin": [ { "gen": { "height": 380575 } } ], "vout": [ { "amount": 33650957081, "target": { "key": "5fb1d7af6b9dcf5f91ef15ead5ada2a947e4a47a385a7dc92a2ca3b6475c0e1a" } } ], "extra": [ 1, 103, 30, 250, 134, 148, 237, 8, 230, 211, 255, 203, 255, 59, 71, 4, 114, 110, 164, 253, 101, 251, 195, 235, 99, 52, 209, 191, 231, 39, 229, 159, 191, 2, 17, 0, 0, 0, 3, 229, 159, 93, 7, 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