← previous blocknext block →recent activity
Analyzing
Block #107,805,520
16 transactions · 14 stateful · 2026-09-25 05:08:01 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #107,805,520 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
10w011w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcd60863…48ea
0x34b655…2a6f
4 touches
1 conflict
0x7bd229ad…63b2
0x34b655…2a6f
4 touches
1 conflict
0xd739490d…821e
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf5dc501b…831c
0x34b655…2a6f
4 touches
1 conflict
0x301e1c77…9e30
0x34b655…2a6f
2 touches
0 conflicts
0x5176bd55…4f0e
0x34b655…2a6f
2 touches
0 conflicts
0x7c7110ee…aebe
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xfcd60863f2…0448ea
Audit this contract →
← previous block·next block →recent activity