Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0ab5bde901cb0d5b185c1be73854b4d9d378b30e709358a779b74bb73d7e9b3

Tx prefix hash: 632996ed4df2cb61e4dc092dbc253099769d474adfaf182a8730f0a4efcd9b10
Tx public key: e7bc3452a207f9ab1d2e9d3319937448fa2382045b79c164602db2399f5bed9d
Timestamp: 1722709801 Timestamp [UCT]: 2024-08-03 18:30:01 Age [y:d:h:m:s]: 00:177:01:06:28
Block: 1080019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126417 RingCT/type: yes/0
Extra: 01e7bc3452a207f9ab1d2e9d3319937448fa2382045b79c164602db2399f5bed9d02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b12fb685211abea25ba2a7a793f4049e03a33dcf071be4e75a6bd472eada3501 0.600000000000 1553216 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": 1080029, "vin": [ { "gen": { "height": 1080019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b12fb685211abea25ba2a7a793f4049e03a33dcf071be4e75a6bd472eada3501" } } ], "extra": [ 1, 231, 188, 52, 82, 162, 7, 249, 171, 29, 46, 157, 51, 25, 147, 116, 72, 250, 35, 130, 4, 91, 121, 193, 100, 96, 45, 178, 57, 159, 91, 237, 157, 2, 17, 0, 0, 0, 1, 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