Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cec1d6bc2712e2dcddd85215378e445ea539a7e9a4a1b6dca6c65e498084b5bf

Tx prefix hash: 568e0df716a31cc649ffb5c3704f42be6977f6959d559f30fe5cd89e91988f79
Tx public key: c4804f4b1eaa1f804a274659ce68b99fe29e3bcde9e82c1f4aeae1c1222744a0
Timestamp: 1752410024 Timestamp [UCT]: 2025-07-13 12:33:44 Age [y:d:h:m:s]: 00:169:00:35:01
Block: 1324599 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119586 RingCT/type: yes/0
Extra: 01c4804f4b1eaa1f804a274659ce68b99fe29e3bcde9e82c1f4aeae1c1222744a0021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e579d62c4af2a3861442836edb1704d0fc7f95bdc5785e6ddde51c80d0eda47 0.600000000000 1812342 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": 1324609, "vin": [ { "gen": { "height": 1324599 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e579d62c4af2a3861442836edb1704d0fc7f95bdc5785e6ddde51c80d0eda47" } } ], "extra": [ 1, 196, 128, 79, 75, 30, 170, 31, 128, 74, 39, 70, 89, 206, 104, 185, 159, 226, 158, 59, 205, 233, 232, 44, 31, 74, 234, 225, 193, 34, 39, 68, 160, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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