← previous blocknext block →recent activity
Analyzing
Block #107,666,159
25 transactions · 22 stateful · 2026-09-24 17:25:45 UTC
Parallelism
84/100
Blocked
32%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,666,159 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w212w016w017w118w119w220w123w024w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9420d123…4d0b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x29134c7d…c58b
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x6e360a5d…8836
0x34b655…2a6f
4 touches
1 conflict
0x78d9f293…ac54
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 0x9420d12345…294d0b
Audit this contract →
← previous block·next block →recent activity