Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9aa5067e1f0529708303119fd9415abc50de3772bbf08cf31549fa15af2b322f

Tx prefix hash: 586e86ff50f2400b88c6472795f9fcabfa0f67bc3d35405a836e5c1b5a68a0a5
Tx public key: bd0048e3ba2076c7d15ee018ee929ed2dc1be9e0aaaa0e355ad00dc07e569f87
Timestamp: 1582509161 Timestamp [UCT]: 2020-02-24 01:52:41 Age [y:d:h:m:s]: 05:103:08:17:09
Block: 71139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1227280 RingCT/type: yes/0
Extra: 01bd0048e3ba2076c7d15ee018ee929ed2dc1be9e0aaaa0e355ad00dc07e569f8702110000000156c366d3000000000000000000

1 output(s) for total of 356.687396445000 dcy

stealth address amount amount idx
00: 1cb82fb307e068a907ad11fbbe6d3e22d61a742e810c2c35f2749d779057bbbb 356.687396445000 131464 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": 71149, "vin": [ { "gen": { "height": 71139 } } ], "vout": [ { "amount": 356687396445, "target": { "key": "1cb82fb307e068a907ad11fbbe6d3e22d61a742e810c2c35f2749d779057bbbb" } } ], "extra": [ 1, 189, 0, 72, 227, 186, 32, 118, 199, 209, 94, 224, 24, 238, 146, 158, 210, 220, 27, 233, 224, 170, 170, 14, 53, 90, 208, 13, 192, 126, 86, 159, 135, 2, 17, 0, 0, 0, 1, 86, 195, 102, 211, 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