Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a3b6b43e05d7563e44bab25aff3225d1823d7e5aa46aba0b02482e89076baed

Tx prefix hash: d33aa575ed0f8f2115258e80c102240f4e6f3712d8eb1f435e6ef8656c92f0e8
Tx public key: c25fff367bea766d2a8f0f5799dccf5ed814ce32478ba14d48d112352aa03cb3
Timestamp: 1746648076 Timestamp [UCT]: 2025-05-07 20:01:16 Age [y:d:h:m:s]: 00:240:17:54:40
Block: 1277957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169835 RingCT/type: yes/0
Extra: 01c25fff367bea766d2a8f0f5799dccf5ed814ce32478ba14d48d112352aa03cb30211000000031f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 15d57a17186a57babaa97f9d9d679b7623f44c2c26cf7e96f586e8f2a7317d82 0.600000000000 1765316 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": 1277967, "vin": [ { "gen": { "height": 1277957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "15d57a17186a57babaa97f9d9d679b7623f44c2c26cf7e96f586e8f2a7317d82" } } ], "extra": [ 1, 194, 95, 255, 54, 123, 234, 118, 109, 42, 143, 15, 87, 153, 220, 207, 94, 216, 20, 206, 50, 71, 139, 161, 77, 72, 209, 18, 53, 42, 160, 60, 179, 2, 17, 0, 0, 0, 3, 31, 144, 81, 122, 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