Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c9d18a6ca7673f39f397f28a38feda041d5f2cee69e5fdc341d1f79c1abab0b

Tx prefix hash: d4ecefd142bc60d2fae0b0d6cc798bcbca66d5c9ba8a43fdc423f5902098b1f2
Tx public key: 0d6d25cd5ad7003cf9823b5ca5f38e7335f1ffcccea30892cb7bc8deac6321fe
Timestamp: 1719377617 Timestamp [UCT]: 2024-06-26 04:53:37 Age [y:d:h:m:s]: 00:310:16:35:20
Block: 1052382 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222033 RingCT/type: yes/0
Extra: 010d6d25cd5ad7003cf9823b5ca5f38e7335f1ffcccea30892cb7bc8deac6321fe0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc6ad4a0a8fc65bfc71c98156e6e1db5d51f234f43858dacd39943e0c631574c 0.600000000000 1522707 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": 1052392, "vin": [ { "gen": { "height": 1052382 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc6ad4a0a8fc65bfc71c98156e6e1db5d51f234f43858dacd39943e0c631574c" } } ], "extra": [ 1, 13, 109, 37, 205, 90, 215, 0, 60, 249, 130, 59, 92, 165, 243, 142, 115, 53, 241, 255, 204, 206, 163, 8, 146, 203, 123, 200, 222, 172, 99, 33, 254, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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