← previous blocknext block →recent activity
Analyzing
Block #107,806,991
20 transactions · 19 stateful · 2026-09-25 05:15:25 UTC
Parallelism
75/100
Blocked
42%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,806,991 · 20 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
4w06w19w010w111w212w313w414w015w117w218w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5fabef3…9e1f
0x40c49f…2af0
10 touches
10 conflicts
0x2b54cadb…4425
0xd18b7e…414b
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x6518075e…2b17
0x2a68ba…90c5
10 touches
10 conflicts
0x4292a836…9ed5
0x34b655…2a6f
4 touches
1 conflict
0x0407a759…51b7
0x34b655…2a6f
4 touches
1 conflict
0x1724ead4…3efd
0x34b655…2a6f
4 touches
1 conflict
0x1ecb37ef…54dc
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: 0x40c49f17…d22af0
10 conflicts on slot 0xc5fabef39c…259e1f
Audit this contract →
← previous block·next block →recent activity