Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5795ee0d7b6a96b4f6312a04a772a1ecd82d5fdfb3b3ef4a3d6c44d9af355e5e

Tx prefix hash: 767ede2663b8128704c91a23eee539b3ddda89455d5c174d9254de492c94976d
Tx public key: e43b0a04114d0e3cf447e983cb47e864f275737b24cafb23326900b1d46deb2f
Timestamp: 1735534423 Timestamp [UCT]: 2024-12-30 04:53:43 Age [y:d:h:m:s]: 01:009:09:29:02
Block: 1186208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265184 RingCT/type: yes/0
Extra: 01e43b0a04114d0e3cf447e983cb47e864f275737b24cafb23326900b1d46deb2f021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ce1a5ce5c4297bdc5122dfc154c79e770e69a55bc874004a0db26f4b3354117 0.600000000000 1672687 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": 1186218, "vin": [ { "gen": { "height": 1186208 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ce1a5ce5c4297bdc5122dfc154c79e770e69a55bc874004a0db26f4b3354117" } } ], "extra": [ 1, 228, 59, 10, 4, 17, 77, 14, 60, 244, 71, 233, 131, 203, 71, 232, 100, 242, 117, 115, 123, 36, 202, 251, 35, 50, 105, 0, 177, 212, 109, 235, 47, 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