Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 420b639741bfe397b480580d505be8cbdc82933a5179801703fc0dbd30c172bc

Tx prefix hash: 79ccfec7136c1eb018c49fd8d369f9f5c618c6eb2bd93556d3581038ab38bbc8
Tx public key: bc4c845f0545d411e3ed12acd7597880a442ad08cb9e05367cd73351e0b3d31d
Timestamp: 1698342623 Timestamp [UCT]: 2023-10-26 17:50:23 Age [y:d:h:m:s]: 01:083:04:10:50
Block: 878225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320657 RingCT/type: yes/0
Extra: 01bc4c845f0545d411e3ed12acd7597880a442ad08cb9e05367cd73351e0b3d31d0211000000014b8f5122000000000000000000

1 output(s) for total of 0.755224415000 dcy

stealth address amount amount idx
00: 02cb8c83b647fa0ae098c3f515f3024848d0772b5621dc1c37c42d4ca211bbed 0.755224415000 1333651 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": 878235, "vin": [ { "gen": { "height": 878225 } } ], "vout": [ { "amount": 755224415, "target": { "key": "02cb8c83b647fa0ae098c3f515f3024848d0772b5621dc1c37c42d4ca211bbed" } } ], "extra": [ 1, 188, 76, 132, 95, 5, 69, 212, 17, 227, 237, 18, 172, 215, 89, 120, 128, 164, 66, 173, 8, 203, 158, 5, 54, 124, 215, 51, 81, 224, 179, 211, 29, 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