Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd6779ea4847a4955dca89c76fb4f1fab3ac303c06ed015f1abbaef8d14c5020

Tx prefix hash: a7af9f63e0f53ab5762aebf65f8f0351afb24a1050d3e2af76d52acb2ac6e3da
Tx public key: 9f2dd3236abce75b9963463817a98b78d32d4fa2ddd6025515637d6034bdceb8
Timestamp: 1712094041 Timestamp [UCT]: 2024-04-02 21:40:41 Age [y:d:h:m:s]: 00:235:20:23:35
Block: 991980 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168870 RingCT/type: yes/0
Extra: 019f2dd3236abce75b9963463817a98b78d32d4fa2ddd6025515637d6034bdceb802110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3334f2b4c2abc4e80dbce047288088c346e34a3b4e7fe04e1be8848cd1b9a293 0.600000000000 1452316 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": 991990, "vin": [ { "gen": { "height": 991980 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3334f2b4c2abc4e80dbce047288088c346e34a3b4e7fe04e1be8848cd1b9a293" } } ], "extra": [ 1, 159, 45, 211, 35, 106, 188, 231, 91, 153, 99, 70, 56, 23, 169, 139, 120, 211, 45, 79, 162, 221, 214, 2, 85, 21, 99, 125, 96, 52, 189, 206, 184, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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