← previous blocknext block →recent activity
Analyzing
Block #107,440,530
13 transactions · 13 stateful · 2026-09-23 22:28:51 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #107,440,530 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w27w08w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5969523e…5191
0x34b655…2a6f
6 touches
3 conflicts
0xe9693c23…43cc
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1b1
0x37db7f…ec7b
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x5c3fa017…70c8
0x34b655…2a6f
4 touches
1 conflict
0xa3d78e5e…bb33
0x34b655…2a6f
4 touches
1 conflict
0xb066c72c…87d2
0x34b655…2a6f
4 touches
1 conflict
0xb94a2ed9…d989
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
3 conflicts on slot 0x5969523e5a…035191
Audit this contract →
← previous block·next block →recent activity