Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b6671b88f9e72bd3ad428ccc486d0086e3bcc1abe1335b2e6c3f4ba94676851

Tx prefix hash: 55f8c254713cabf5ae72aa3d64a996fe2ac5e7084cb40d9dd7c45141c55c4387
Tx public key: 4c0e91838f6ffcd69a2ab7222d12979400c2a2f6f3711ba46d0faea78fe5499b
Timestamp: 1757992784 Timestamp [UCT]: 2025-09-16 03:19:44 Age [y:d:h:m:s]: 00:098:17:25:28
Block: 1369426 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70682 RingCT/type: yes/0
Extra: 014c0e91838f6ffcd69a2ab7222d12979400c2a2f6f3711ba46d0faea78fe5499b021100000002b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 248af1c77065912a248bcaf263f97f48a9664bff0cb10900222b985cb5f3c3f8 0.600000000000 1857501 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": 1369436, "vin": [ { "gen": { "height": 1369426 } } ], "vout": [ { "amount": 600000000, "target": { "key": "248af1c77065912a248bcaf263f97f48a9664bff0cb10900222b985cb5f3c3f8" } } ], "extra": [ 1, 76, 14, 145, 131, 143, 111, 252, 214, 154, 42, 183, 34, 45, 18, 151, 148, 0, 194, 162, 246, 243, 113, 27, 164, 109, 15, 174, 167, 143, 229, 73, 155, 2, 17, 0, 0, 0, 2, 178, 247, 132, 196, 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