← previous blocknext block →recent activity
Analyzing
Block #107,817,151
25 transactions · 20 stateful · 2026-09-25 06:06:32 UTC
Parallelism
80/100
Blocked
60%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,817,151 · 25 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
1w02w13w04w15w07w29w110w011w112w213w114w215w116w317w424w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5cf4d55d…c588
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0xc7679110…572d
0x34b655…2a6f
6 touches
3 conflicts
0x2ce2d49e…d18c
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 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
6 conflicts on slot 0x5cf4d55d39…13c588
Audit this contract →
← previous block·next block →recent activity