← previous blocknext block →recent activity
Analyzing
Block #107,815,926
21 transactions · 20 stateful · 2026-09-25 06:00:22 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,815,926 · 21 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
1w02w13w14w27w210w211w313w414w517w018w119w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7679110…572d
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x232b0b19…d946
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xf899a9c9…4a41
0x34b655…2a6f
6 touches
3 conflicts
0x4a1553d9…655d
0x34b655…2a6f
6 touches
3 conflicts
0x5cf4d55d…c588
0x34b655…2a6f
6 touches
3 conflicts
0xb8337efb…68ca
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
3 conflicts on slot 0xc7679110cf…22572d
Audit this contract →
← previous block·next block →recent activity