Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 269ce5bc3147ec8d38b74f1886ac824ce86bf28994b9e34b6134fa4297e902b2

Tx prefix hash: 7b6babd846d7fa41ef64fcb3a75196e51254a5b9c6e58225c8602e1cec87c442
Tx public key: 13c6e961bcbd1aeb32556fc81d3c8c6cd75dc333946157a745d2f340e35b3cb9
Timestamp: 1752493844 Timestamp [UCT]: 2025-07-14 11:50:44 Age [y:d:h:m:s]: 00:124:14:37:26
Block: 1325291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87788 RingCT/type: yes/0
Extra: 0113c6e961bcbd1aeb32556fc81d3c8c6cd75dc333946157a745d2f340e35b3cb902110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72ffe5ffb4e1b3ee629437d641dda5114b86d3ec14a4aa1f105e6682deeb1e0e 0.600000000000 1813036 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": 1325301, "vin": [ { "gen": { "height": 1325291 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72ffe5ffb4e1b3ee629437d641dda5114b86d3ec14a4aa1f105e6682deeb1e0e" } } ], "extra": [ 1, 19, 198, 233, 97, 188, 189, 26, 235, 50, 85, 111, 200, 29, 60, 140, 108, 215, 93, 195, 51, 148, 97, 87, 167, 69, 210, 243, 64, 227, 91, 60, 185, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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