Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae2cbb1fd981c219e6f9daf00d15500ce2d0b21589a6f0001f1bd5851dd24775

Tx prefix hash: eea263de9cfcc9ee830338543e3f2641f7064c8ae684bf5cff2ee8e48f523675
Tx public key: 9d86fe0608c7412de42bc7cf765545e02b59592926a8ed681e615c358a09a3d9
Timestamp: 1721416400 Timestamp [UCT]: 2024-07-19 19:13:20 Age [y:d:h:m:s]: 01:112:07:03:01
Block: 1069305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338752 RingCT/type: yes/0
Extra: 019d86fe0608c7412de42bc7cf765545e02b59592926a8ed681e615c358a09a3d9021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87849c022bdc19964b3e74640f5069e1c00e8ab9531c41ce7e413b3fdbca0ccf 0.600000000000 1540682 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": 1069315, "vin": [ { "gen": { "height": 1069305 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87849c022bdc19964b3e74640f5069e1c00e8ab9531c41ce7e413b3fdbca0ccf" } } ], "extra": [ 1, 157, 134, 254, 6, 8, 199, 65, 45, 228, 43, 199, 207, 118, 85, 69, 224, 43, 89, 89, 41, 38, 168, 237, 104, 30, 97, 92, 53, 138, 9, 163, 217, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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