Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d94a37fb4d438ff2039b78c7811c8fe068472169c2a45e7c245438f5d4e1432c

Tx prefix hash: f4f77bc93b4919ef064d8715518319a25b08c832e496066b444bbf5099e450d7
Tx public key: 826b04bb46f0e58b32f4ae238f80f7a7eb29de4acb33480d4d50a0357a8dbdbf
Timestamp: 1762161016 Timestamp [UCT]: 2025-11-03 09:10:16 Age [y:d:h:m:s]: 00:050:09:23:55
Block: 1403961 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36079 RingCT/type: yes/0
Extra: 01826b04bb46f0e58b32f4ae238f80f7a7eb29de4acb33480d4d50a0357a8dbdbf0211000000055dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a523538114c29795eeb4072ad88e53923a8bc153eb0527ab70a68b3bb6c41fd 0.600000000000 1892318 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": 1403971, "vin": [ { "gen": { "height": 1403961 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a523538114c29795eeb4072ad88e53923a8bc153eb0527ab70a68b3bb6c41fd" } } ], "extra": [ 1, 130, 107, 4, 187, 70, 240, 229, 139, 50, 244, 174, 35, 143, 128, 247, 167, 235, 41, 222, 74, 203, 51, 72, 13, 77, 80, 160, 53, 122, 141, 189, 191, 2, 17, 0, 0, 0, 5, 93, 251, 190, 42, 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