← previous blocknext block →recent activity
Analyzing
Block #83,623,087
25 transactions · 21 stateful · 2026-06-25 15:00:10 UTC
Parallelism
72/100
Blocked
43%
Avg conflicts / tx
1.08
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,623,087 · 25 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
1w06w07w18w29w310w411w512w619w124w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0xcbef1a2f…f83e
0x34b655…2a6f
8 touches
6 conflicts
0x0835adb5…ad83
0x34b655…2a6f
8 touches
6 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
6 touches
3 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x1385199e…fec8
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