Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7aa4e9e75ac2ebefd462c1fe4c69592086225726f3d3f11cfbb73c4b8004d718

Tx prefix hash: 7f619aaf21b4fa5894df4e44469cb07f9bc26c3745011d949bb790021c724482
Tx public key: caf460573b6e48eb8146b76b3ef46bb0066d63c47632a301323d612dc8b2433a
Timestamp: 1578831615 Timestamp [UCT]: 2020-01-12 12:20:15 Age [y:d:h:m:s]: 05:120:07:49:20
Block: 43936 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1236162 RingCT/type: yes/0
Extra: 01caf460573b6e48eb8146b76b3ef46bb0066d63c47632a301323d612dc8b2433a0211000000134943cd9f000000000000000000

1 output(s) for total of 438.962833146000 dcy

stealth address amount amount idx
00: 375cfb7911da159ba46d74f701c245d66a4f9b9db011bd69e82222afe53f40f1 438.962833146000 79766 of 0

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": 43946, "vin": [ { "gen": { "height": 43936 } } ], "vout": [ { "amount": 438962833146, "target": { "key": "375cfb7911da159ba46d74f701c245d66a4f9b9db011bd69e82222afe53f40f1" } } ], "extra": [ 1, 202, 244, 96, 87, 59, 110, 72, 235, 129, 70, 183, 107, 62, 244, 107, 176, 6, 109, 99, 196, 118, 50, 163, 1, 50, 61, 97, 45, 200, 178, 67, 58, 2, 17, 0, 0, 0, 19, 73, 67, 205, 159, 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