← previous blocknext block →recent activity
Analyzing
Block #107,806,941
24 transactions · 18 stateful · 2026-09-25 05:15:10 UTC
Parallelism
71/100
Blocked
56%
Avg conflicts / tx
0.92
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #107,806,941 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w18w29w310w411w312w413w514w622w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b0611f7…e63a
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xb15c58ec…bd83
0x34b655…2a6f
6 touches
3 conflicts
0x1724ead4…3efd
0x34b655…2a6f
4 touches
1 conflict
0x1c9136d3…7c71
0x34b655…2a6f
4 touches
1 conflict
0x1f84ce8a…5acc
0x34b655…2a6f
4 touches
1 conflict
0x35d3e1fe…6ac8
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
6 conflicts on slot 0x0b0611f77e…54e63a
Audit this contract →
← previous block·next block →recent activity