Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a8a0e2dcb1eeb5e2f61c32d190ad123c4cf86028f61ed1aa7a9cfbe60e401aa

Tx prefix hash: 0abbaec5d672663f246fb551cb79596328dfaaf484a4c04497e7a2780e4a297a
Tx public key: 600206b9194629e2b53dbdf8da264b64fa176b5649984c79cbe4b4eb11850833
Timestamp: 1699685961 Timestamp [UCT]: 2023-11-11 06:59:21 Age [y:d:h:m:s]: 02:078:19:44:04
Block: 889145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 576023 RingCT/type: yes/0
Extra: 01600206b9194629e2b53dbdf8da264b64fa176b5649984c79cbe4b4eb1185083302110000000333af99f4000000000000000000

1 output(s) for total of 0.694853921000 dcy

stealth address amount amount idx
00: 4a50161476e9265f221e40b769e28925c4ac384fdb3ee3abbea62d18c19e62a8 0.694853921000 1345122 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": 889155, "vin": [ { "gen": { "height": 889145 } } ], "vout": [ { "amount": 694853921, "target": { "key": "4a50161476e9265f221e40b769e28925c4ac384fdb3ee3abbea62d18c19e62a8" } } ], "extra": [ 1, 96, 2, 6, 185, 25, 70, 41, 226, 181, 61, 189, 248, 218, 38, 75, 100, 250, 23, 107, 86, 73, 152, 76, 121, 203, 228, 180, 235, 17, 133, 8, 51, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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