← previous blocknext block →recent activity
Analyzing
Block #83,401,952
20 transactions · 20 stateful · 2026-06-24 14:24:19 UTC
Parallelism
65/100
Blocked
45%
Avg conflicts / tx
1.25
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,401,952 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w38w49w110w511w612w013w017w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0xec7b070f…db9a
0x34b655…2a6f
6 touches
3 conflicts
0x0835adb5…ad83
0x34b655…2a6f
4 touches
1 conflict
0x33df44c2…b815
0x34b655…2a6f
4 touches
1 conflict
0x42a5df10…2e70
0x34b655…2a6f
4 touches
1 conflict
0x4abf223d…0915
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
0x65bb8d8c…8bb0
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
21 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity