Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c88c511019b94b2ca04fdabaecdaf29f3c8c26fe77cbe43987f8f47384e9d3f2

Tx prefix hash: f9749244da355fd400af4963b46e8b10d6a04581bdc3bc65d5ae701757a9a900
Tx public key: abb88fb202bfbea7819c7fdc329e856bd4a23019343a723c6f34abc2b54c7108
Timestamp: 1710049422 Timestamp [UCT]: 2024-03-10 05:43:42 Age [y:d:h:m:s]: 01:030:10:22:30
Block: 975071 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282731 RingCT/type: yes/0
Extra: 01abb88fb202bfbea7819c7fdc329e856bd4a23019343a723c6f34abc2b54c710802110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37f938be686f2cf1fce5583911db6885ec816a5cdef47210ef03d90164d83fe5 0.600000000000 1435042 of 15

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": 975081, "vin": [ { "gen": { "height": 975071 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37f938be686f2cf1fce5583911db6885ec816a5cdef47210ef03d90164d83fe5" } } ], "extra": [ 1, 171, 184, 143, 178, 2, 191, 190, 167, 129, 156, 127, 220, 50, 158, 133, 107, 212, 162, 48, 25, 52, 58, 114, 60, 111, 52, 171, 194, 181, 76, 113, 8, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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