Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a6c95d6487d417c0e1c13dfa0b34adc05147228cd2795b67684ba95895381ea

Tx prefix hash: bcd192ac2cccbde8c91f9a486d796206a115dbfb4329bd88b2679550f4aaa33c
Tx public key: c21fc7a587c7d494b89dfca1d5e53ea0bef397065e31816e1c08f488455d9785
Timestamp: 1645453084 Timestamp [UCT]: 2022-02-21 14:18:04 Age [y:d:h:m:s]: 03:256:09:46:18
Block: 443387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 961017 RingCT/type: yes/0
Extra: 01c21fc7a587c7d494b89dfca1d5e53ea0bef397065e31816e1c08f488455d97850211000000055eb576c5000000000000000000

1 output(s) for total of 20.838914786000 dcy

stealth address amount amount idx
00: 7477c7e66a863700d11d1c3acb855b342458b13adbdc2641bee2bfa090957020 20.838914786000 856406 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": 443397, "vin": [ { "gen": { "height": 443387 } } ], "vout": [ { "amount": 20838914786, "target": { "key": "7477c7e66a863700d11d1c3acb855b342458b13adbdc2641bee2bfa090957020" } } ], "extra": [ 1, 194, 31, 199, 165, 135, 199, 212, 148, 184, 157, 252, 161, 213, 229, 62, 160, 190, 243, 151, 6, 94, 49, 129, 110, 28, 8, 244, 136, 69, 93, 151, 133, 2, 17, 0, 0, 0, 5, 94, 181, 118, 197, 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