Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b01339c0c7246f0f0f50c8b0ea34847363f000b30075d7b8d79d8d65e6017798

Tx prefix hash: e2dfbe6db364c77799be24740c473fb6faf3e3f1b49fd9adc16c9f1088dfc7f1
Tx public key: 75563700784c12feadfae81119dbcb6534e2a4be9a232efb4a0140bee6ad64cf
Timestamp: 1710268093 Timestamp [UCT]: 2024-03-12 18:28:13 Age [y:d:h:m:s]: 01:056:21:25:37
Block: 976879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301659 RingCT/type: yes/0
Extra: 0175563700784c12feadfae81119dbcb6534e2a4be9a232efb4a0140bee6ad64cf0211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7d6bf42681639dac59ddfa80c8371785fd29a9a4fdee5c5620a235601307e52 0.600000000000 1436878 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": 976889, "vin": [ { "gen": { "height": 976879 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7d6bf42681639dac59ddfa80c8371785fd29a9a4fdee5c5620a235601307e52" } } ], "extra": [ 1, 117, 86, 55, 0, 120, 76, 18, 254, 173, 250, 232, 17, 25, 219, 203, 101, 52, 226, 164, 190, 154, 35, 46, 251, 74, 1, 64, 190, 230, 173, 100, 207, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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