Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2e484e38aa4bf1f2501fab9529050a7f5b04420b4a569293d159eb1436a57f3

Tx prefix hash: efed6328cf3ad0deb0fbc9220a944a45f2fc19900017e153a79656960a63d6b4
Tx public key: edf0e61196180292e5191bde277ee53c0937e8b49ccf44c8967d47e5a76e9a01
Timestamp: 1700493334 Timestamp [UCT]: 2023-11-20 15:15:34 Age [y:d:h:m:s]: 01:061:21:43:49
Block: 895832 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305597 RingCT/type: yes/0
Extra: 01edf0e61196180292e5191bde277ee53c0937e8b49ccf44c8967d47e5a76e9a010211000000024b8f5122000000000000000000

1 output(s) for total of 0.660293004000 dcy

stealth address amount amount idx
00: 1b14e889236c517e3ce65499f8e64eca495c7b09db46a4a085e151e71e3589c8 0.660293004000 1352079 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": 895842, "vin": [ { "gen": { "height": 895832 } } ], "vout": [ { "amount": 660293004, "target": { "key": "1b14e889236c517e3ce65499f8e64eca495c7b09db46a4a085e151e71e3589c8" } } ], "extra": [ 1, 237, 240, 230, 17, 150, 24, 2, 146, 229, 25, 27, 222, 39, 126, 229, 60, 9, 55, 232, 180, 156, 207, 68, 200, 150, 125, 71, 229, 167, 110, 154, 1, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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