Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8fd51903cbb6f99474316cf7ad3abf792865f8b9fc6678ea6c4761f5dbb8bcea

Tx prefix hash: e647fe0740d96bb7dd9e8856e5bfba3022711aa861a4dfd3c45a96c847a76ecd
Tx public key: 9f43cd7361aedba8bced05de5eb8d70e5a75118d6ce382656319549f41a886cc
Timestamp: 1674613400 Timestamp [UCT]: 2023-01-25 02:23:20 Age [y:d:h:m:s]: 02:084:16:01:08
Block: 682156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 582164 RingCT/type: yes/0
Extra: 019f43cd7361aedba8bced05de5eb8d70e5a75118d6ce382656319549f41a886cc0211000000035029cbac000000000000000000

1 output(s) for total of 3.370807372000 dcy

stealth address amount amount idx
00: 79a25b5ef18858fb244f5fd33187e32a1e2e00a753eaa14b6d05c6cd8183e09e 3.370807372000 1124271 of 0

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": 682166, "vin": [ { "gen": { "height": 682156 } } ], "vout": [ { "amount": 3370807372, "target": { "key": "79a25b5ef18858fb244f5fd33187e32a1e2e00a753eaa14b6d05c6cd8183e09e" } } ], "extra": [ 1, 159, 67, 205, 115, 97, 174, 219, 168, 188, 237, 5, 222, 94, 184, 215, 14, 90, 117, 17, 141, 108, 227, 130, 101, 99, 25, 84, 159, 65, 168, 134, 204, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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