Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18d76fa51f3d84b9664025797c76751654543074d7e80b1e7163a7639a69b534

Tx prefix hash: 5387c0a582d4f06e4c51308e3a75d82d407796dab6b09e5a23aa5f7f121acb71
Tx public key: b2f88f11f790d24dbcd3a4f04da313cac36c52b764fc1bf30ca9b6574ae66e3d
Timestamp: 1577166061 Timestamp [UCT]: 2019-12-24 05:41:01 Age [y:d:h:m:s]: 05:013:22:20:45
Block: 30406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1160079 RingCT/type: yes/0
Extra: 01b2f88f11f790d24dbcd3a4f04da313cac36c52b764fc1bf30ca9b6574ae66e3d0211000000028a2ee0d9000000000000000000

1 output(s) for total of 486.690827771000 dcy

stealth address amount amount idx
00: 79074fb0e99bb2ed3931802914277da0b11cb874dc1edfcb7f2c6ef9c3179e4b 486.690827771000 50214 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": 30416, "vin": [ { "gen": { "height": 30406 } } ], "vout": [ { "amount": 486690827771, "target": { "key": "79074fb0e99bb2ed3931802914277da0b11cb874dc1edfcb7f2c6ef9c3179e4b" } } ], "extra": [ 1, 178, 248, 143, 17, 247, 144, 210, 77, 188, 211, 164, 240, 77, 163, 19, 202, 195, 108, 82, 183, 100, 252, 27, 243, 12, 169, 182, 87, 74, 230, 110, 61, 2, 17, 0, 0, 0, 2, 138, 46, 224, 217, 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