Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78475cabfa99bf41c9808878f4872caa364c63ffbc5ca5add4612f8e28d80381

Tx prefix hash: 718ce9ce271aa68d4398158775168d4f258e924f20af9644676aab01a1494db7
Tx public key: 3b8ec639bae4ebf6b7a2ec8480af65604c461bed18f0de5ee144fcc136b3b5e7
Timestamp: 1635984684 Timestamp [UCT]: 2021-11-04 00:11:24 Age [y:d:h:m:s]: 03:131:12:24:40
Block: 366798 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 872334 RingCT/type: yes/0
Extra: 013b8ec639bae4ebf6b7a2ec8480af65604c461bed18f0de5ee144fcc136b3b5e702110000000df56b629f000000000000000000

1 output(s) for total of 37.380607908000 dcy

stealth address amount amount idx
00: 992a241e56a9dd415a8e1f06afc5c998cdc2c3414d9531844193a1d8fd8a01d1 37.380607908000 744460 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": 366808, "vin": [ { "gen": { "height": 366798 } } ], "vout": [ { "amount": 37380607908, "target": { "key": "992a241e56a9dd415a8e1f06afc5c998cdc2c3414d9531844193a1d8fd8a01d1" } } ], "extra": [ 1, 59, 142, 198, 57, 186, 228, 235, 246, 183, 162, 236, 132, 128, 175, 101, 96, 76, 70, 27, 237, 24, 240, 222, 94, 225, 68, 252, 193, 54, 179, 181, 231, 2, 17, 0, 0, 0, 13, 245, 107, 98, 159, 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