Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b47efcff2096dd1143e4bec6141f06813b225c10a09e7e4a3cbfae45059d6e2

Tx prefix hash: ac73cbf4d2f8fd00d6a698640c6051ba4903cf93b0f97e29e57be466b091d50e
Tx public key: 08c82463df517ae14bf543d19b287c4dc4015d2c0bb47f7b97a32d8b63782e0d
Timestamp: 1709181053 Timestamp [UCT]: 2024-02-29 04:30:53 Age [y:d:h:m:s]: 01:102:17:47:20
Block: 967866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334486 RingCT/type: yes/0
Extra: 0108c82463df517ae14bf543d19b287c4dc4015d2c0bb47f7b97a32d8b63782e0d0211000000040546d7d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1f2139d4b1ea4dbf5fb05a240852230e629100a1ad39257271525050c3ab341 0.600000000000 1427657 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": 967876, "vin": [ { "gen": { "height": 967866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1f2139d4b1ea4dbf5fb05a240852230e629100a1ad39257271525050c3ab341" } } ], "extra": [ 1, 8, 200, 36, 99, 223, 81, 122, 225, 75, 245, 67, 209, 155, 40, 124, 77, 196, 1, 93, 44, 11, 180, 127, 123, 151, 163, 45, 139, 99, 120, 46, 13, 2, 17, 0, 0, 0, 4, 5, 70, 215, 208, 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