Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71ca8d3c95d0f04d675f08aa485dea6563472e850fed26e42fbf686f29913043

Tx prefix hash: 31d3297d59d66972230580e8a6ed0502eb08798fd0f4e952768e2c718e72487b
Tx public key: 59049dc5aa8e85ce9b28e2daca484d7290d8f37c4827bbe33ac2e585a3ffb06f
Timestamp: 1737140532 Timestamp [UCT]: 2025-01-17 19:02:12 Age [y:d:h:m:s]: 00:339:05:02:30
Block: 1199510 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239986 RingCT/type: yes/0
Extra: 0159049dc5aa8e85ce9b28e2daca484d7290d8f37c4827bbe33ac2e585a3ffb06f0211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2068b41cfbe3139a7f3d61e7025f9086779d17846b953ca6db69058dfdf7cdb 0.600000000000 1686141 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": 1199520, "vin": [ { "gen": { "height": 1199510 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2068b41cfbe3139a7f3d61e7025f9086779d17846b953ca6db69058dfdf7cdb" } } ], "extra": [ 1, 89, 4, 157, 197, 170, 142, 133, 206, 155, 40, 226, 218, 202, 72, 77, 114, 144, 216, 243, 124, 72, 39, 187, 227, 58, 194, 229, 133, 163, 255, 176, 111, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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