Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2cf93207fdcdf92bf320e3cb4f0fdf9be6cda87b31b4f92884f737d936737de

Tx prefix hash: a02d850e9b34a72963695ececc1de69b105125a43c75f9f3cc68cf1daf54c9b8
Tx public key: 378eff89e27707578fcdf192698e6f0be8f9fdded9d60f1dc91f6f6f95a7c23e
Timestamp: 1755438748 Timestamp [UCT]: 2025-08-17 13:52:28 Age [y:d:h:m:s]: 00:130:21:49:21
Block: 1348535 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93461 RingCT/type: yes/0
Extra: 01378eff89e27707578fcdf192698e6f0be8f9fdded9d60f1dc91f6f6f95a7c23e021100000005a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c34d55de194abb70792f9e9ba4d0174d97234abaad878eb3243d7c446e8e0a54 0.600000000000 1836462 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": 1348545, "vin": [ { "gen": { "height": 1348535 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c34d55de194abb70792f9e9ba4d0174d97234abaad878eb3243d7c446e8e0a54" } } ], "extra": [ 1, 55, 142, 255, 137, 226, 119, 7, 87, 143, 205, 241, 146, 105, 142, 111, 11, 232, 249, 253, 222, 217, 214, 15, 29, 201, 31, 111, 111, 149, 167, 194, 62, 2, 17, 0, 0, 0, 5, 161, 29, 186, 152, 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