Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ca9b80ccb46eb3c45cae0073bca306795671ebe528dac0f75dc14d6d5dc4611

Tx prefix hash: 8ed3ff5eb0dbb4175e648dc9eb11b7699b9fb4ba954fe1b565dfb1d50e50c2c9
Tx public key: aa025a9a8c4febf51ff1dea022a501e526389eef13a56b10a0aa7f0ed30d3817
Timestamp: 1745676710 Timestamp [UCT]: 2025-04-26 14:11:50 Age [y:d:h:m:s]: 00:015:00:21:14
Block: 1269921 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10734 RingCT/type: yes/0
Extra: 01aa025a9a8c4febf51ff1dea022a501e526389eef13a56b10a0aa7f0ed30d3817021100000005dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f432b72b010747d2cb02f0b169d61ccfba6b657fa557fe0eb57f48c64d6aae09 0.600000000000 1757160 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": 1269931, "vin": [ { "gen": { "height": 1269921 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f432b72b010747d2cb02f0b169d61ccfba6b657fa557fe0eb57f48c64d6aae09" } } ], "extra": [ 1, 170, 2, 90, 154, 140, 79, 235, 245, 31, 241, 222, 160, 34, 165, 1, 229, 38, 56, 158, 239, 19, 165, 107, 16, 160, 170, 127, 14, 211, 13, 56, 23, 2, 17, 0, 0, 0, 5, 219, 181, 113, 193, 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