Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b62f33506018221ad1f06db91a4b7ce48e7a52891b0bdd46f950d2a54c6b01e

Tx prefix hash: 74fd6936560930279f21874c83d58cef037d946f0117a041b2da776663a04aba
Tx public key: b6ee1b090083e65371414aa4b6a3b6bff1be91f7fe174f6d7a943397868fc428
Timestamp: 1729660592 Timestamp [UCT]: 2024-10-23 05:16:32 Age [y:d:h:m:s]: 00:032:09:41:09
Block: 1137613 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23150 RingCT/type: yes/0
Extra: 01b6ee1b090083e65371414aa4b6a3b6bff1be91f7fe174f6d7a943397868fc428021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af9076e59cc52e3f82f609ac705de7bfd7477904529cb327f9b60fb26d43c61f 0.600000000000 1621136 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": 1137623, "vin": [ { "gen": { "height": 1137613 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af9076e59cc52e3f82f609ac705de7bfd7477904529cb327f9b60fb26d43c61f" } } ], "extra": [ 1, 182, 238, 27, 9, 0, 131, 230, 83, 113, 65, 74, 164, 182, 163, 182, 191, 241, 190, 145, 247, 254, 23, 79, 109, 122, 148, 51, 151, 134, 143, 196, 40, 2, 17, 0, 0, 0, 2, 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