← previous blocknext block →recent activity
Analyzing
Block #107,982,412
27 transactions · 26 stateful · 2026-09-25 19:58:27 UTC
Parallelism
78/100
Blocked
35%
Avg conflicts / tx
0.85
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,982,412 · 27 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
1w02w13w24w313w014w115w216w317w421w024w525w026w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xde61791c…b4c2
0x40c49f…2af0
11 touches
15 conflicts
0x6518075e…2b17
0x2a68ba…90c5
11 touches
15 conflicts
0x2b54cadb…4425
0xd18b7e…414b
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0xf5dc501b…831c
0x34b655…2a6f
8 touches
6 conflicts
0x7bd229ad…63b2
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x555b9368…2989
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
15 conflicts on slot 0xde61791c72…bab4c2
Audit this contract →
← previous block·next block →recent activity