Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 200f0d4cf549fe1a7bd5a2bd44554f36c3881f9569ab881e8713d9bce5ed9e8c

Tx prefix hash: fe1c54f25de4f1411c0d3f0e097cd154ac4c6381851601e023aefb249aea8c79
Tx public key: a47d3daaeb2a2244083e5cf7210c5c20d5d1972f71364694db7b835a0b83729b
Timestamp: 1763295068 Timestamp [UCT]: 2025-11-16 12:11:08 Age [y:d:h:m:s]: 00:037:11:22:02
Block: 1413367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26817 RingCT/type: yes/0
Extra: 01a47d3daaeb2a2244083e5cf7210c5c20d5d1972f71364694db7b835a0b83729b021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0229274f5ccbb115a6962114b21c750b61fce799bd01361b76b5c80f04fcf9e6 0.600000000000 1901846 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": 1413377, "vin": [ { "gen": { "height": 1413367 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0229274f5ccbb115a6962114b21c750b61fce799bd01361b76b5c80f04fcf9e6" } } ], "extra": [ 1, 164, 125, 61, 170, 235, 42, 34, 68, 8, 62, 92, 247, 33, 12, 92, 32, 213, 209, 151, 47, 113, 54, 70, 148, 219, 123, 131, 90, 11, 131, 114, 155, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 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