Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e162398545a22f30e0ce9040b16df53d10771350ff8a6dca562feed57bc8ae01

Tx prefix hash: 18b48f8e1ba8f1dc1c6ff955c860348958ec70bf40c48936758db8fa55990dac
Tx public key: dd51e6b1bc16a33c3ce6e03b54fe6d4efd8ed956670858b4f18c4775776d5c4c
Timestamp: 1737309931 Timestamp [UCT]: 2025-01-19 18:05:31 Age [y:d:h:m:s]: 00:149:03:42:36
Block: 1200880 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106331 RingCT/type: yes/0
Extra: 01dd51e6b1bc16a33c3ce6e03b54fe6d4efd8ed956670858b4f18c4775776d5c4c021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 483002c3dfe7f1f9345f034cb88da3800666915bfca09e8ee923fd7e9811de70 0.600000000000 1687527 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": 1200890, "vin": [ { "gen": { "height": 1200880 } } ], "vout": [ { "amount": 600000000, "target": { "key": "483002c3dfe7f1f9345f034cb88da3800666915bfca09e8ee923fd7e9811de70" } } ], "extra": [ 1, 221, 81, 230, 177, 188, 22, 163, 60, 60, 230, 224, 59, 84, 254, 109, 78, 253, 142, 217, 86, 103, 8, 88, 180, 241, 140, 71, 117, 119, 109, 92, 76, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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