Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc9d3f190891ae01aa5428909664c371d3b85ac60e502f91e3e533faa80a36d9

Tx prefix hash: b8172270eec4da89008a6d7dc95f80e8df9c5f29105f624a413a80602edf7a4e
Tx public key: e8a2012a08cdce7da0de05d981018e251917da012c2578caddbe8bd7a40d64d2
Timestamp: 1721859750 Timestamp [UCT]: 2024-07-24 22:22:30 Age [y:d:h:m:s]: 00:258:20:17:21
Block: 1072967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184912 RingCT/type: yes/0
Extra: 01e8a2012a08cdce7da0de05d981018e251917da012c2578caddbe8bd7a40d64d202110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53c39d937aecebbbe321a1ae76b5dc3f70d50c40824b35bbc8cfcabc57a37833 0.600000000000 1545464 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": 1072977, "vin": [ { "gen": { "height": 1072967 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53c39d937aecebbbe321a1ae76b5dc3f70d50c40824b35bbc8cfcabc57a37833" } } ], "extra": [ 1, 232, 162, 1, 42, 8, 205, 206, 125, 160, 222, 5, 217, 129, 1, 142, 37, 25, 23, 218, 1, 44, 37, 120, 202, 221, 190, 139, 215, 164, 13, 100, 210, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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