Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1787ec868d38dbb76a78979d95a5094d2e616d4f412f718e95987a607385ae35

Tx prefix hash: 0a1db945ab963fb2711e87281ac56ed390fefe110c007c9b7263951c744fad02
Tx public key: 39924d20c0add5dcadffc21a3bdb04a3d10b042aa3535dc11d0267ce1a363dd9
Timestamp: 1715388789 Timestamp [UCT]: 2024-05-11 00:53:09 Age [y:d:h:m:s]: 00:133:11:32:13
Block: 1019348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95599 RingCT/type: yes/0
Extra: 0139924d20c0add5dcadffc21a3bdb04a3d10b042aa3535dc11d0267ce1a363dd9021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1777eb3199f5b9c949bb55fdbb6cbb75e1a38bd2db7d8c7cd43a9bf3304df012 0.600000000000 1483293 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": 1019358, "vin": [ { "gen": { "height": 1019348 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1777eb3199f5b9c949bb55fdbb6cbb75e1a38bd2db7d8c7cd43a9bf3304df012" } } ], "extra": [ 1, 57, 146, 77, 32, 192, 173, 213, 220, 173, 255, 194, 26, 59, 219, 4, 163, 209, 11, 4, 42, 163, 83, 93, 193, 29, 2, 103, 206, 26, 54, 61, 217, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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