Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44f9d4c98c8a824cb0fc321573a3cb9cdc1ef332b065268749dc97e417fbf2de

Tx prefix hash: 868c1659a60d4f8c4965f2f5abe8aa10772c4d44fb66b087392aa0be4e1e1f02
Tx public key: fe5b33a80e066caa0c5e6e285fff08ec876fea960af73af2af273857edd90074
Timestamp: 1762167791 Timestamp [UCT]: 2025-11-03 11:03:11 Age [y:d:h:m:s]: 00:007:10:31:11
Block: 1404016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5335 RingCT/type: yes/0
Extra: 01fe5b33a80e066caa0c5e6e285fff08ec876fea960af73af2af273857edd900740211000000075dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67578de60d8fe9786e3e9e432a54dea639184b24fe15ec7aa5b191621201f3ca 0.600000000000 1892373 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": 1404026, "vin": [ { "gen": { "height": 1404016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67578de60d8fe9786e3e9e432a54dea639184b24fe15ec7aa5b191621201f3ca" } } ], "extra": [ 1, 254, 91, 51, 168, 14, 6, 108, 170, 12, 94, 110, 40, 95, 255, 8, 236, 135, 111, 234, 150, 10, 247, 58, 242, 175, 39, 56, 87, 237, 217, 0, 116, 2, 17, 0, 0, 0, 7, 93, 251, 190, 42, 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