Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a431754eb8f22aec5bc8e87b60faa2c49ef8c38ac1c909347fb0ebed4d1b588f

Tx prefix hash: 1a8d59c819dd3c4e929ffd011cba3bf16aae4b18c106ded9c68a6a5aae2cfb2e
Tx public key: addf9b3de71cde5e54772ac21ab7b4bc81e2af294f9427243839d80e3864399f
Timestamp: 1754490304 Timestamp [UCT]: 2025-08-06 14:25:04 Age [y:d:h:m:s]: 00:105:10:01:46
Block: 1341519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74362 RingCT/type: yes/0
Extra: 01addf9b3de71cde5e54772ac21ab7b4bc81e2af294f9427243839d80e3864399f021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 28fb5c7a7e6c00e2a717ea88ed7fb7a419c290bcd2eaa9b6a7226f84cf45582d 0.600000000000 1829344 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": 1341529, "vin": [ { "gen": { "height": 1341519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "28fb5c7a7e6c00e2a717ea88ed7fb7a419c290bcd2eaa9b6a7226f84cf45582d" } } ], "extra": [ 1, 173, 223, 155, 61, 231, 28, 222, 94, 84, 119, 42, 194, 26, 183, 180, 188, 129, 226, 175, 41, 79, 148, 39, 36, 56, 57, 216, 14, 56, 100, 57, 159, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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