Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53b6705724a6e0b221e248b8f1ed208d8a335b266edbe620736c9b7701307f8e

Tx prefix hash: 1ad405143a7fca04897ca63c1f8ce9ab8f9f7ba92d04ed17a175807fb733efd6
Tx public key: c61c824471a8db455148aa81d1cd17212fcdf71e3b97af0c900344928258c904
Timestamp: 1712851693 Timestamp [UCT]: 2024-04-11 16:08:13 Age [y:d:h:m:s]: 00:319:20:13:34
Block: 998269 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228655 RingCT/type: yes/0
Extra: 01c61c824471a8db455148aa81d1cd17212fcdf71e3b97af0c900344928258c9040211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45320c0dbc9740356bb424eadaf4b991a1e01b2aad213a6a3840ab4ea7a7f34d 0.600000000000 1458715 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": 998279, "vin": [ { "gen": { "height": 998269 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45320c0dbc9740356bb424eadaf4b991a1e01b2aad213a6a3840ab4ea7a7f34d" } } ], "extra": [ 1, 198, 28, 130, 68, 113, 168, 219, 69, 81, 72, 170, 129, 209, 205, 23, 33, 47, 205, 247, 30, 59, 151, 175, 12, 144, 3, 68, 146, 130, 88, 201, 4, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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