Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68aa7214e1d52f1b2ab3a92c317457d35526e5171a04deb59538188d53101e18

Tx prefix hash: 142854412ce8709d14c8cd684b862e3567fa5aceca4f3bb9ef4aec5c5cf12f9e
Tx public key: 76d67feb65cea0c98f9ed968e3c7f65f1c0f574af444cf58e959f927a0eb39f2
Timestamp: 1746932558 Timestamp [UCT]: 2025-05-11 03:02:38 Age [y:d:h:m:s]: 00:193:05:16:25
Block: 1280308 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135806 RingCT/type: yes/0
Extra: 0176d67feb65cea0c98f9ed968e3c7f65f1c0f574af444cf58e959f927a0eb39f20211000000031f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8e296915f170e06835c0a55ab3cdb986f008592770fb9c89f4f2422d5eb897d 0.600000000000 1767691 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": 1280318, "vin": [ { "gen": { "height": 1280308 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8e296915f170e06835c0a55ab3cdb986f008592770fb9c89f4f2422d5eb897d" } } ], "extra": [ 1, 118, 214, 127, 235, 101, 206, 160, 201, 143, 158, 217, 104, 227, 199, 246, 95, 28, 15, 87, 74, 244, 68, 207, 88, 233, 89, 249, 39, 160, 235, 57, 242, 2, 17, 0, 0, 0, 3, 31, 144, 81, 122, 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