Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1ddaea3ab2dc05dba1ea6e8453384492cd51c24f9464e29265f87c6d4f69930

Tx prefix hash: 75c624509a75ab3c9111b60666f04d64823ffa805990b02b61dba4e9fb6d9f5d
Tx public key: ffc0d398741b90ffb5bfa8135df12007ac681f278d0fd7f871a5f3bdb9521d54
Timestamp: 1765827663 Timestamp [UCT]: 2025-12-15 19:41:03 Age [y:d:h:m:s]: 00:006:12:52:03
Block: 1434346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4683 RingCT/type: yes/0
Extra: 01ffc0d398741b90ffb5bfa8135df12007ac681f278d0fd7f871a5f3bdb9521d540211000000027b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ace9533e9458e8bc673a06927b6aa8d34aa11cfdcbe68fee25a962409a24ef5 0.600000000000 1923137 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": 1434356, "vin": [ { "gen": { "height": 1434346 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ace9533e9458e8bc673a06927b6aa8d34aa11cfdcbe68fee25a962409a24ef5" } } ], "extra": [ 1, 255, 192, 211, 152, 116, 27, 144, 255, 181, 191, 168, 19, 93, 241, 32, 7, 172, 104, 31, 39, 141, 15, 215, 248, 113, 165, 243, 189, 185, 82, 29, 84, 2, 17, 0, 0, 0, 2, 123, 30, 81, 172, 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