Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf358a00b97645a8e16852cf56aee9f98e79c0296c51219c05358f15323ed0a3

Tx prefix hash: ab606db0b639f7619da2f9fd7fed2824d4c1ccec34da7a03810df6d3bbda91c3
Tx public key: 9bf8d0a1b110c05e10aaf49f88866eb4f454ee12b01d6c31dd978160edb3699e
Timestamp: 1761498025 Timestamp [UCT]: 2025-10-26 17:00:25 Age [y:d:h:m:s]: 00:014:02:42:19
Block: 1398479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10104 RingCT/type: yes/0
Extra: 019bf8d0a1b110c05e10aaf49f88866eb4f454ee12b01d6c31dd978160edb3699e02110000000425a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ad83c00d2f8ff590cd4d393fd9ebb4a322f40cb5ef1e31aa06186e7068a743e 0.600000000000 1886778 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": 1398489, "vin": [ { "gen": { "height": 1398479 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ad83c00d2f8ff590cd4d393fd9ebb4a322f40cb5ef1e31aa06186e7068a743e" } } ], "extra": [ 1, 155, 248, 208, 161, 177, 16, 192, 94, 16, 170, 244, 159, 136, 134, 110, 180, 244, 84, 238, 18, 176, 29, 108, 49, 221, 151, 129, 96, 237, 179, 105, 158, 2, 17, 0, 0, 0, 4, 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