Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 962a6f5a6dbc7cb4f3be3c11fca902d04a03278ab0caa0272f8ef19172d7d933

Tx prefix hash: 128b4c9b99621b8123fd3bbce65d6200875fc59fa652274c7e1ccf23b5376524
Tx public key: 70a3366aa5aa919071be6f680167ca533dc67664596f09912dbd80b5d581def2
Timestamp: 1724327281 Timestamp [UCT]: 2024-08-22 11:48:01 Age [y:d:h:m:s]: 00:231:02:56:35
Block: 1093446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165039 RingCT/type: yes/0
Extra: 0170a3366aa5aa919071be6f680167ca533dc67664596f09912dbd80b5d581def2021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0230aa846ab0d5eab9492068a6f9da8287ec7f67274caeb8c4655afa69f30e3 0.600000000000 1568391 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": 1093456, "vin": [ { "gen": { "height": 1093446 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0230aa846ab0d5eab9492068a6f9da8287ec7f67274caeb8c4655afa69f30e3" } } ], "extra": [ 1, 112, 163, 54, 106, 165, 170, 145, 144, 113, 190, 111, 104, 1, 103, 202, 83, 61, 198, 118, 100, 89, 111, 9, 145, 45, 189, 128, 181, 213, 129, 222, 242, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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