Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81f957e86ebfdf2de8cc2a75006c777a86b5342c1f153867553574636f5a82c7

Tx prefix hash: f1732f6d62e6060819fb88b056dfabc8caa5f34edd9bc241ec099c61349060ec
Tx public key: 42bde6a578b79f5bebdfeeb9ba9ddfb7d1a2c3edb061f640ca6cfdc5eb778a9c
Timestamp: 1757456223 Timestamp [UCT]: 2025-09-09 22:17:03 Age [y:d:h:m:s]: 00:065:09:22:40
Block: 1365008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46801 RingCT/type: yes/0
Extra: 0142bde6a578b79f5bebdfeeb9ba9ddfb7d1a2c3edb061f640ca6cfdc5eb778a9c021100000017ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9a878e7ce984da8a238d4bb13a0f18b17481c984b81b1202d241974f855d4bb 0.600000000000 1853047 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": 1365018, "vin": [ { "gen": { "height": 1365008 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9a878e7ce984da8a238d4bb13a0f18b17481c984b81b1202d241974f855d4bb" } } ], "extra": [ 1, 66, 189, 230, 165, 120, 183, 159, 91, 235, 223, 238, 185, 186, 157, 223, 183, 209, 162, 195, 237, 176, 97, 246, 64, 202, 108, 253, 197, 235, 119, 138, 156, 2, 17, 0, 0, 0, 23, 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