Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4d287b9028054043452880c8de0c14111e5f6cca8e48b64d2464064396eaff8

Tx prefix hash: 3806b1878c894a948adee39ad2e858f7aa6ca43e1dc3a67cb37d849f8d547df6
Tx public key: 08b63c28c2dad9cc575fd82ae877ac4787d60bdb436bec313fd3b74f0742534e
Timestamp: 1713967560 Timestamp [UCT]: 2024-04-24 14:06:00 Age [y:d:h:m:s]: 00:357:02:08:05
Block: 1007541 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255282 RingCT/type: yes/0
Extra: 0108b63c28c2dad9cc575fd82ae877ac4787d60bdb436bec313fd3b74f0742534e0211000000010011055b000000000000000000

1 output(s) for total of 0.615590000000 dcy

stealth address amount amount idx
00: 6e54198300a2bcf964685b9be10dae62036a6d9dfbe12dd472608f46c6dc29b3 0.615590000000 1468911 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": 1007551, "vin": [ { "gen": { "height": 1007541 } } ], "vout": [ { "amount": 615590000, "target": { "key": "6e54198300a2bcf964685b9be10dae62036a6d9dfbe12dd472608f46c6dc29b3" } } ], "extra": [ 1, 8, 182, 60, 40, 194, 218, 217, 204, 87, 95, 216, 42, 232, 119, 172, 71, 135, 214, 11, 219, 67, 107, 236, 49, 63, 211, 183, 79, 7, 66, 83, 78, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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