Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0a45070ec08f9ccd6192f686715b7fb3b725f68d86cacbad5b0a9bdafb618cc

Tx prefix hash: dc8fd3ca71720d5a181b3485555e13b507a04b778926ad845447092582683b8c
Tx public key: 8c6a30f8e92a21c3c4bfd8c92531620e7d0bcc1c728a463fb55a5e92aec14f3d
Timestamp: 1685814363 Timestamp [UCT]: 2023-06-03 17:46:03 Age [y:d:h:m:s]: 01:307:09:25:35
Block: 774381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 480890 RingCT/type: yes/0
Extra: 018c6a30f8e92a21c3c4bfd8c92531620e7d0bcc1c728a463fb55a5e92aec14f3d0211000000014b8f5122000000000000000000

1 output(s) for total of 1.667840262000 dcy

stealth address amount amount idx
00: 07275e14d104d943281c2075b00322d0f2e3988bb8353423402253c394a4e07d 1.667840262000 1223856 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": 774391, "vin": [ { "gen": { "height": 774381 } } ], "vout": [ { "amount": 1667840262, "target": { "key": "07275e14d104d943281c2075b00322d0f2e3988bb8353423402253c394a4e07d" } } ], "extra": [ 1, 140, 106, 48, 248, 233, 42, 33, 195, 196, 191, 216, 201, 37, 49, 98, 14, 125, 11, 204, 28, 114, 138, 70, 63, 181, 90, 94, 146, 174, 193, 79, 61, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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