Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6030d087f5b260a3c35b2c07005c65b7b4eddd461bf301cec7fc8ba3c2e60b7

Tx prefix hash: fc2150b725c180c6fb26b03dfb7ab683df83a6b31573ee1b2b1b8a74e693b0a3
Tx public key: 2245ca4e239facced2655518564d6cd0d9b91183635a54da9a0729ac2f024657
Timestamp: 1763091832 Timestamp [UCT]: 2025-11-14 03:43:52 Age [y:d:h:m:s]: 00:047:17:50:16
Block: 1411684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34181 RingCT/type: yes/0
Extra: 012245ca4e239facced2655518564d6cd0d9b91183635a54da9a0729ac2f024657021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f87c11e0f8aa6a70fe1c7fbd73867247ca52ab7531083d4322f411e1b317f4d 0.600000000000 1900147 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": 1411694, "vin": [ { "gen": { "height": 1411684 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f87c11e0f8aa6a70fe1c7fbd73867247ca52ab7531083d4322f411e1b317f4d" } } ], "extra": [ 1, 34, 69, 202, 78, 35, 159, 172, 206, 210, 101, 85, 24, 86, 77, 108, 208, 217, 185, 17, 131, 99, 90, 84, 218, 154, 7, 41, 172, 47, 2, 70, 87, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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