Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb9150cf3eb85dcd2dbe7ad78d15fa621c012a465f0b36b0f0b9055aa0765344

Tx prefix hash: ab21227db97cc685b749dfbef52a37c83f1693ae8fad1e1f1be87696e351812f
Tx public key: d3dfca6630ea70b32ac99197330a2f24a7d9a823373dab93b82a98b58d91a80e
Timestamp: 1743665921 Timestamp [UCT]: 2025-04-03 07:38:41 Age [y:d:h:m:s]: 00:279:04:27:03
Block: 1253255 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197351 RingCT/type: yes/0
Extra: 01d3dfca6630ea70b32ac99197330a2f24a7d9a823373dab93b82a98b58d91a80e021100000004a2ed016b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1aa4652a7fe0a32d0190b049493ed12907c31aa49875107c3db38b45d7f2bbb2 0.600000000000 1740336 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": 1253265, "vin": [ { "gen": { "height": 1253255 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1aa4652a7fe0a32d0190b049493ed12907c31aa49875107c3db38b45d7f2bbb2" } } ], "extra": [ 1, 211, 223, 202, 102, 48, 234, 112, 179, 42, 201, 145, 151, 51, 10, 47, 36, 167, 217, 168, 35, 55, 61, 171, 147, 184, 42, 152, 181, 141, 145, 168, 14, 2, 17, 0, 0, 0, 4, 162, 237, 1, 107, 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