Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 040fca818c70608b2fc173722afc79c433cc17e1d1b74d6457864458f08bef8c

Tx prefix hash: db4fdaec30d4ea89d0e1aefb0d5103a381f69bf7be457dd7b01de964b4eb3daf
Tx public key: 95a7b60f9a9ac123422dcf6f3c88e3f4ab61887685da37ee9a0a2428df7869a6
Timestamp: 1751397505 Timestamp [UCT]: 2025-07-01 19:18:25 Age [y:d:h:m:s]: 00:142:14:17:40
Block: 1316730 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100127 RingCT/type: yes/0
Extra: 0195a7b60f9a9ac123422dcf6f3c88e3f4ab61887685da37ee9a0a2428df7869a6021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fac3ca62d21e938140f14bef25e051bda88dc3e7f10ec457181a1a4600493946 0.600000000000 1804393 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": 1316740, "vin": [ { "gen": { "height": 1316730 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fac3ca62d21e938140f14bef25e051bda88dc3e7f10ec457181a1a4600493946" } } ], "extra": [ 1, 149, 167, 182, 15, 154, 154, 193, 35, 66, 45, 207, 111, 60, 136, 227, 244, 171, 97, 136, 118, 133, 218, 55, 238, 154, 10, 36, 40, 223, 120, 105, 166, 2, 17, 0, 0, 0, 1, 191, 81, 178, 162, 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