Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a8285568e56b25439d2c296e8dfbef1f95e3e536896cefeadd6ec367972b9b8

Tx prefix hash: bb4fd501fffa6bc51419a6874bd79abccf780913744bbca05e9fcf2cffbb46fb
Tx public key: 8a2c35f048a5fbd5ff2dab21c83a8ee56620ca4470ebf06e11408fa55a17a1ba
Timestamp: 1651200279 Timestamp [UCT]: 2022-04-29 02:44:39 Age [y:d:h:m:s]: 03:186:22:21:10
Block: 490350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 911950 RingCT/type: yes/0
Extra: 018a2c35f048a5fbd5ff2dab21c83a8ee56620ca4470ebf06e11408fa55a17a1ba021100000001c9067537000000000000000000

1 output(s) for total of 14.563545456000 dcy

stealth address amount amount idx
00: a6d7b6193828975a0a7c9db00ff1817527802b0f6e26b7eb5e48106399a554e0 14.563545456000 913335 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": 490360, "vin": [ { "gen": { "height": 490350 } } ], "vout": [ { "amount": 14563545456, "target": { "key": "a6d7b6193828975a0a7c9db00ff1817527802b0f6e26b7eb5e48106399a554e0" } } ], "extra": [ 1, 138, 44, 53, 240, 72, 165, 251, 213, 255, 45, 171, 33, 200, 58, 142, 229, 102, 32, 202, 68, 112, 235, 240, 110, 17, 64, 143, 165, 90, 23, 161, 186, 2, 17, 0, 0, 0, 1, 201, 6, 117, 55, 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