Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ca4b7932345cf5c3fb2bac5fbde3c0d2c4543d6cb64fc63161a8b94851c7722

Tx prefix hash: ff74d664557b29a9255b5d0dc8570fe997224a7eb552750d42a9e661a55a869f
Tx public key: fd494d97e47cb51e9b1d0db3ba51d91aec8443bbf75e4339a80c1a0ab96e4f8a
Timestamp: 1685329309 Timestamp [UCT]: 2023-05-29 03:01:49 Age [y:d:h:m:s]: 01:273:09:28:11
Block: 770368 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 456565 RingCT/type: yes/0
Extra: 01fd494d97e47cb51e9b1d0db3ba51d91aec8443bbf75e4339a80c1a0ab96e4f8a021100000004e6d27f9c000000000000000000

1 output(s) for total of 1.719694073000 dcy

stealth address amount amount idx
00: 024dbdc94d02af456c295a463fb07c33145ec96d11f04c4c965d063f09d82355 1.719694073000 1219673 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": 770378, "vin": [ { "gen": { "height": 770368 } } ], "vout": [ { "amount": 1719694073, "target": { "key": "024dbdc94d02af456c295a463fb07c33145ec96d11f04c4c965d063f09d82355" } } ], "extra": [ 1, 253, 73, 77, 151, 228, 124, 181, 30, 155, 29, 13, 179, 186, 81, 217, 26, 236, 132, 67, 187, 247, 94, 67, 57, 168, 12, 26, 10, 185, 110, 79, 138, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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