← previous blocknext block →recent activity
Analyzing
Block #83,624,432
17 transactions · 15 stateful · 2026-06-25 15:09:10 UTC
Parallelism
65/100
Blocked
40%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,624,432 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w414w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92793b0e…b68e
0x34b655…2a6f
10 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
8 touches
6 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0xd4a2cf20…e2b0
0x34b655…2a6f
6 touches
3 conflicts
0xb20ad85e…1e79
0x34b655…2a6f
6 touches
3 conflicts
0x82e625e0…e9d6
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
10 conflicts on slot 0x92793b0ede…0ab68e
Audit this contract →
← previous block·next block →recent activity