Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d633e077a3aa6a6b12ee8269c1cbe05e4bc494f628b33ad334e001c84c32a83

Tx prefix hash: 7abf3ef316be30b0869a05bb888102a4db601fbe1c6bfc5100edf3113f4c6e72
Tx public key: 14d9b9f4b27fe6b249e5e335ce8648c83d351f66bacc759f28c8dbdd8c1d7fb3
Timestamp: 1702304452 Timestamp [UCT]: 2023-12-11 14:20:52 Age [y:d:h:m:s]: 01:156:10:12:04
Block: 910845 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372966 RingCT/type: yes/0
Extra: 0114d9b9f4b27fe6b249e5e335ce8648c83d351f66bacc759f28c8dbdd8c1d7fb302110000000533af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f3135c863e6ae85124534fce5a88b057b36dc7a503113de680fff1d76206791 0.600000000000 1368020 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": 910855, "vin": [ { "gen": { "height": 910845 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f3135c863e6ae85124534fce5a88b057b36dc7a503113de680fff1d76206791" } } ], "extra": [ 1, 20, 217, 185, 244, 178, 127, 230, 178, 73, 229, 227, 53, 206, 134, 72, 200, 61, 53, 31, 102, 186, 204, 117, 159, 40, 200, 219, 221, 140, 29, 127, 179, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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