← previous blocknext block →recent activity
Analyzing
Block #107,849,558
19 transactions · 14 stateful · 2026-09-25 08:49:39 UTC
Parallelism
68/100
Blocked
36%
Avg conflicts / tx
0.47
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,849,558 · 19 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
3w06w07w18w29w310w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba522812…1f1f
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x3949ab7a…0b85
0x34b655…2a6f
6 touches
3 conflicts
0x2b76a1fb…fdfc
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x813beb96…822d
0x34b655…2a6f
4 touches
1 conflict
0x0311862a…7c5c
0x34b655…2a6f
4 touches
1 conflict
0x839d9801…0419
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 0xba52281226…3a1f1f
Audit this contract →
← previous block·next block →recent activity