← previous blocknext block →recent activity
Analyzing
Block #107,823,139
27 transactions · 26 stateful · 2026-09-25 06:36:41 UTC
Parallelism
81/100
Blocked
23%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,823,139 · 27 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w111w012w117w018w119w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66fc0764…05fd
0x34b655…2a6f
10 touches
10 conflicts
0xbbb11e9e…89bb
0x34b655…2a6f
10 touches
10 conflicts
0xba9f9225…2ead
0x34b655…2a6f
6 touches
3 conflicts
0x422cccbc…9b18
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x90a021f0…f922
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x7c80d7be…b7dc
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 0x66fc076467…c305fd
Audit this contract →
← previous block·next block →recent activity