← previous blocknext block →recent activity
Analyzing
Block #107,823,389
17 transactions · 17 stateful · 2026-09-25 06:37:56 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,823,389 · 17 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
5w06w17w08w19w210w111w212w313w414w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x72083f0d…082a
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x481db2dd…cc35
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6b97ded2…f70b
0x34b655…2a6f
4 touches
1 conflict
0x7ad7e7c3…293b
0x34b655…2a6f
4 touches
1 conflict
0x7ed4080f…0f62
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 0x42522e76ce…082592
Audit this contract →
← previous block·next block →recent activity