Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3dfca434b1b25b6d7e0d5a0736b6570a56bdf43d50d60b31c2c5e967b24dcb8

Tx prefix hash: 2282670246764dcc81825c4a41e3b2cb77f4a8cef7e1ed9d474de62ad775683b
Tx public key: 51afdd34572cb687b66cc2d5dce52b4d82d9ecb316899b351418bf03bf9873ba
Timestamp: 1758306175 Timestamp [UCT]: 2025-09-19 18:22:55 Age [y:d:h:m:s]: 00:131:14:33:36
Block: 1372025 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94052 RingCT/type: yes/0
Extra: 0151afdd34572cb687b66cc2d5dce52b4d82d9ecb316899b351418bf03bf9873ba021100000002ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85cd5cb6274058e5bc8ec0e0629d3082d60b2f367f9c1cabd2a3a5c532fb7fc6 0.600000000000 1860110 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": 1372035, "vin": [ { "gen": { "height": 1372025 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85cd5cb6274058e5bc8ec0e0629d3082d60b2f367f9c1cabd2a3a5c532fb7fc6" } } ], "extra": [ 1, 81, 175, 221, 52, 87, 44, 182, 135, 182, 108, 194, 213, 220, 229, 43, 77, 130, 217, 236, 179, 22, 137, 155, 53, 20, 24, 191, 3, 191, 152, 115, 186, 2, 17, 0, 0, 0, 2, 173, 121, 72, 208, 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