Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8bb6040c07da7cd09d8e0435a21c425e4780170685b0a4c92bcf6991f5dce237

Tx prefix hash: 01e971ff33b2277279c6ff58853ba2d422589b9828a4f8eb509b4480fcd01e5c
Tx public key: 17da712ad874ceeb6aa86522e56f59caa38da951c862e76118e55f98447b6383
Timestamp: 1733350785 Timestamp [UCT]: 2024-12-04 22:19:45 Age [y:d:h:m:s]: 00:114:08:42:40
Block: 1168137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81528 RingCT/type: yes/0
Extra: 0117da712ad874ceeb6aa86522e56f59caa38da951c862e76118e55f98447b6383021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0db0f255b3fd67cb2fe902c953d10c4ae19bc716bca6735d515c0f103f390ccf 0.600000000000 1653844 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": 1168147, "vin": [ { "gen": { "height": 1168137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0db0f255b3fd67cb2fe902c953d10c4ae19bc716bca6735d515c0f103f390ccf" } } ], "extra": [ 1, 23, 218, 113, 42, 216, 116, 206, 235, 106, 168, 101, 34, 229, 111, 89, 202, 163, 141, 169, 81, 200, 98, 231, 97, 24, 229, 95, 152, 68, 123, 99, 131, 2, 17, 0, 0, 0, 1, 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