← previous blocknext block →recent activity
Analyzing
Block #107,849,574
18 transactions · 18 stateful · 2026-09-25 08:49:44 UTC
Parallelism
56/100
Blocked
61%
Avg conflicts / tx
1.67
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,849,574 · 18 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
3w04w15w26w18w29w310w411w512w513w614w717w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba522812…1f1f
0x34b655…2a6f
10 touches
10 conflicts
0x2b76a1fb…fdfc
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xee796382…2855
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x2902f960…84cc
0x34b655…2a6f
6 touches
3 conflicts
0xab41643c…f9bf
0x34b655…2a6f
6 touches
3 conflicts
0xc4c059d8…185d
0x34b655…2a6f
6 touches
3 conflicts
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 0xba52281226…3a1f1f
Audit this contract →
← previous block·next block →recent activity