Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2612d864195bff3404f2e9d4202fc3de2c96b0c4746282fff1d164733e5f342

Tx prefix hash: f90cc7a1c35b795d3170442daaf08b0a0fddaad121f6d560720915cbf2b40e1f
Tx public key: 78c1d8f8b0608ae184b94cf11852176495d676685235c8e540b9c7dd0b8ffbe9
Timestamp: 1658726260 Timestamp [UCT]: 2022-07-25 05:17:40 Age [y:d:h:m:s]: 02:188:18:48:16
Block: 551173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 656102 RingCT/type: yes/0
Extra: 0178c1d8f8b0608ae184b94cf11852176495d676685235c8e540b9c7dd0b8ffbe9021100000002ec6d1a1a000000000000000000

1 output(s) for total of 9.156619735000 dcy

stealth address amount amount idx
00: ee479dbea4c26da513827a7256ad8718ad269745518ecaa9874f70c2e18b8624 9.156619735000 982739 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": 551183, "vin": [ { "gen": { "height": 551173 } } ], "vout": [ { "amount": 9156619735, "target": { "key": "ee479dbea4c26da513827a7256ad8718ad269745518ecaa9874f70c2e18b8624" } } ], "extra": [ 1, 120, 193, 216, 248, 176, 96, 138, 225, 132, 185, 76, 241, 24, 82, 23, 100, 149, 214, 118, 104, 82, 53, 200, 229, 64, 185, 199, 221, 11, 143, 251, 233, 2, 17, 0, 0, 0, 2, 236, 109, 26, 26, 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