Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f456dc4c2b9c40a5e4a4e5169d9899611c3454f97a100dfa0fd88542eab53961

Tx prefix hash: 06ca6d4c0e8b3a4c61ca1db36f6596e9bc5ae1951133030f141827f0499e0150
Tx public key: c91bcffdc108840c9f116acf38450d54602562ef4a9e9ed9fd64025506eb279b
Timestamp: 1729885049 Timestamp [UCT]: 2024-10-25 19:37:29 Age [y:d:h:m:s]: 00:151:10:41:57
Block: 1139470 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108018 RingCT/type: yes/0
Extra: 01c91bcffdc108840c9f116acf38450d54602562ef4a9e9ed9fd64025506eb279b021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2da373c6cfb4423b5f12d1c5e0336ab06b60c1286ed63c0a14cbc8ebc6089f1 0.600000000000 1623257 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": 1139480, "vin": [ { "gen": { "height": 1139470 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2da373c6cfb4423b5f12d1c5e0336ab06b60c1286ed63c0a14cbc8ebc6089f1" } } ], "extra": [ 1, 201, 27, 207, 253, 193, 8, 132, 12, 159, 17, 106, 207, 56, 69, 13, 84, 96, 37, 98, 239, 74, 158, 158, 217, 253, 100, 2, 85, 6, 235, 39, 155, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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