Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8e52a9c543863795dae6fae656bf18c8026c2e701145a21de1634bea74494c8

Tx prefix hash: 88993f29c692008c1d1256afc41c3ecf49b70577ce13b5f6425a53c71275bcf0
Tx public key: 91f0d6c1e122faba297eaa26d6699452c24b0a2b6a467be820e6a633dd499533
Timestamp: 1751414156 Timestamp [UCT]: 2025-07-01 23:55:56 Age [y:d:h:m:s]: 00:137:13:52:23
Block: 1316866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96539 RingCT/type: yes/0
Extra: 0191f0d6c1e122faba297eaa26d6699452c24b0a2b6a467be820e6a633dd49953302110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c9f965cf1da2d3fe1a3e730be73fb45508932cf2dcf2ba47eac07da2ab6b4e2 0.600000000000 1804529 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": 1316876, "vin": [ { "gen": { "height": 1316866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c9f965cf1da2d3fe1a3e730be73fb45508932cf2dcf2ba47eac07da2ab6b4e2" } } ], "extra": [ 1, 145, 240, 214, 193, 225, 34, 250, 186, 41, 126, 170, 38, 214, 105, 148, 82, 194, 75, 10, 43, 106, 70, 123, 232, 32, 230, 166, 51, 221, 73, 149, 51, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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