Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cea255accc690d620291e62ec7c94d09c689b0b972ad6ee7831016731e013ca0

Tx prefix hash: 2fc133d1f47e864769d62249e6c053b141a6316ff5dca5b01c9123c50f39e538
Tx public key: dd1483f48b8c53577213f7606e8b8ae3b99a15ae8daf1fc5e30fff00a441416f
Timestamp: 1751974489 Timestamp [UCT]: 2025-07-08 11:34:49 Age [y:d:h:m:s]: 00:209:02:54:57
Block: 1321279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147831 RingCT/type: yes/0
Extra: 01dd1483f48b8c53577213f7606e8b8ae3b99a15ae8daf1fc5e30fff00a441416f0211000000038368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d132f24061a53570a45cac43e5b4313dccffda7c4d1a8f73c98af8a77706cb38 0.600000000000 1808984 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": 1321289, "vin": [ { "gen": { "height": 1321279 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d132f24061a53570a45cac43e5b4313dccffda7c4d1a8f73c98af8a77706cb38" } } ], "extra": [ 1, 221, 20, 131, 244, 139, 140, 83, 87, 114, 19, 247, 96, 110, 139, 138, 227, 185, 154, 21, 174, 141, 175, 31, 197, 227, 15, 255, 0, 164, 65, 65, 111, 2, 17, 0, 0, 0, 3, 131, 104, 38, 109, 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