Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ecd903decba9509bd7a12b6bbe73253166107467affb41bc719fb0f052b7f2d8

Tx prefix hash: fed5dd066d0986d2855c53076214f2491e442bbc34a3bfb46b769f7ffe8e5a6e
Tx public key: 9220d4fc75d6d54907692498b0bc0fd1c317033ff23e79289455aea9e3b57cd5
Timestamp: 1764234330 Timestamp [UCT]: 2025-11-27 09:05:30 Age [y:d:h:m:s]: 00:063:07:29:58
Block: 1421157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45146 RingCT/type: yes/0
Extra: 019220d4fc75d6d54907692498b0bc0fd1c317033ff23e79289455aea9e3b57cd5021100000001defb8f18000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63510d799eb3c23b78a1da5f3b059d6648819282cf8e8d500e51fa7d9254a693 0.600000000000 1909714 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": 1421167, "vin": [ { "gen": { "height": 1421157 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63510d799eb3c23b78a1da5f3b059d6648819282cf8e8d500e51fa7d9254a693" } } ], "extra": [ 1, 146, 32, 212, 252, 117, 214, 213, 73, 7, 105, 36, 152, 176, 188, 15, 209, 195, 23, 3, 63, 242, 62, 121, 40, 148, 85, 174, 169, 227, 181, 124, 213, 2, 17, 0, 0, 0, 1, 222, 251, 143, 24, 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