Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c5eb65b6df93f497544f5780696742022f6ce62e803c4395a424a3148b31ea9

Tx prefix hash: bbeaa4853f9a49420d28c083e73964e37fc5fc601a3d1a91d46f5f6f355ed422
Tx public key: e5156880d153ec55a23bd0a1dcb4b4d2e93ec5c401a12daa9546f1dc1c1dec00
Timestamp: 1750343899 Timestamp [UCT]: 2025-06-19 14:38:19 Age [y:d:h:m:s]: 00:155:02:17:56
Block: 1308429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108650 RingCT/type: yes/0
Extra: 01e5156880d153ec55a23bd0a1dcb4b4d2e93ec5c401a12daa9546f1dc1c1dec00021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cee2fb217e8f08578daf6e53d755743f6cce37042761ae70024f634689523e12 0.600000000000 1796042 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": 1308439, "vin": [ { "gen": { "height": 1308429 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cee2fb217e8f08578daf6e53d755743f6cce37042761ae70024f634689523e12" } } ], "extra": [ 1, 229, 21, 104, 128, 209, 83, 236, 85, 162, 59, 208, 161, 220, 180, 180, 210, 233, 62, 197, 196, 1, 161, 45, 170, 149, 70, 241, 220, 28, 29, 236, 0, 2, 17, 0, 0, 0, 1, 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