Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9c4861e913d3dc31d3982140c038e1b45461e85624dff8c6c2857defd337e15

Tx prefix hash: 55ad8af2bfcf4e859870ad7c416b6402016d2a171be130ac76ba79bef567f7af
Tx public key: eedfb569f8becf4e9bdce2c3d31ae3a5ac3c1c1c77bf912e030a57f1d35d0c14
Timestamp: 1698227613 Timestamp [UCT]: 2023-10-25 09:53:33 Age [y:d:h:m:s]: 01:158:00:59:37
Block: 877264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373948 RingCT/type: yes/0
Extra: 01eedfb569f8becf4e9bdce2c3d31ae3a5ac3c1c1c77bf912e030a57f1d35d0c1402110000000733af99f4000000000000000000

1 output(s) for total of 0.760781976000 dcy

stealth address amount amount idx
00: 148f8a68d1c529e422d79b825ae9611aa774f594f480ec3a769a558ac81384e3 0.760781976000 1332634 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": 877274, "vin": [ { "gen": { "height": 877264 } } ], "vout": [ { "amount": 760781976, "target": { "key": "148f8a68d1c529e422d79b825ae9611aa774f594f480ec3a769a558ac81384e3" } } ], "extra": [ 1, 238, 223, 181, 105, 248, 190, 207, 78, 155, 220, 226, 195, 211, 26, 227, 165, 172, 60, 28, 28, 119, 191, 145, 46, 3, 10, 87, 241, 211, 93, 12, 20, 2, 17, 0, 0, 0, 7, 51, 175, 153, 244, 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