Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7f76ca922beeac6d0b268c036ecf807fbd29249cc6e93905e006dcf82df78cf

Tx prefix hash: 35371fb3e8c960071bdff1c263531a961054edfd4190977fe54a2c3aab1dd9f2
Tx public key: bf9f96770f464bd2e62d91eae7aeca8e6a142bf383713ed2ffc7194e209c9839
Timestamp: 1722365566 Timestamp [UCT]: 2024-07-30 18:52:46 Age [y:d:h:m:s]: 00:163:00:51:15
Block: 1077161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116648 RingCT/type: yes/0
Extra: 01bf9f96770f464bd2e62d91eae7aeca8e6a142bf383713ed2ffc7194e209c9839021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b5e394a7046e0a325e46a500ac5218729b4e833b249a9604a5389069e874b91 0.600000000000 1549708 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": 1077171, "vin": [ { "gen": { "height": 1077161 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b5e394a7046e0a325e46a500ac5218729b4e833b249a9604a5389069e874b91" } } ], "extra": [ 1, 191, 159, 150, 119, 15, 70, 75, 210, 230, 45, 145, 234, 231, 174, 202, 142, 106, 20, 43, 243, 131, 113, 62, 210, 255, 199, 25, 78, 32, 156, 152, 57, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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