Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66928f5b8477c0fe9fe5c4383a18f94929ed427d51dcb8fee7b9d8c1063344d5

Tx prefix hash: 8561c49bc10bc0906920819c5e0795388731601e69c4c4284d2f4f9fbb3770c4
Tx public key: b30e10b0b0cf7979b1642f949954e8636b4f9fa63f598e2ad6c64ca6140042aa
Timestamp: 1761214896 Timestamp [UCT]: 2025-10-23 10:21:36 Age [y:d:h:m:s]: 00:072:22:37:28
Block: 1396136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 52236 RingCT/type: yes/0
Extra: 01b30e10b0b0cf7979b1642f949954e8636b4f9fa63f598e2ad6c64ca6140042aa021100000004df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4e5a915ab9f0c195ea04df08a3c02bb99ad747c5e8be3138331034c01378441 0.600000000000 1884421 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": 1396146, "vin": [ { "gen": { "height": 1396136 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4e5a915ab9f0c195ea04df08a3c02bb99ad747c5e8be3138331034c01378441" } } ], "extra": [ 1, 179, 14, 16, 176, 176, 207, 121, 121, 177, 100, 47, 148, 153, 84, 232, 99, 107, 79, 159, 166, 63, 89, 142, 42, 214, 198, 76, 166, 20, 0, 66, 170, 2, 17, 0, 0, 0, 4, 223, 90, 36, 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