← previous blocknext block →recent activity
Analyzing
Block #106,935,800
26 transactions · 25 stateful · 2026-09-22 04:07:55 UTC
Parallelism
69/100
Blocked
40%
Avg conflicts / tx
0.96
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,935,800 · 26 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w28w09w310w411w512w613w716w125w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51087f5a…61f7
0x34b655…2a6f
12 touches
15 conflicts
0x469dac8d…3411
0x34b655…2a6f
10 touches
10 conflicts
0xee192525…bd26
0x34b655…2a6f
10 touches
10 conflicts
0xccebf5c5…8758
0x34b655…2a6f
10 touches
10 conflicts
0xe36a37be…b306
0x34b655…2a6f
6 touches
3 conflicts
0x34eb3605…9253
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x17a7f697…dcb6
0x1b6862…e19c
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
15 conflicts on slot 0x51087f5abf…f061f7
Audit this contract →
← previous block·next block →recent activity