← previous blocknext block →recent activity
Analyzing
Block #107,816,358
22 transactions · 17 stateful · 2026-09-25 06:02:33 UTC
Parallelism
73/100
Blocked
47%
Avg conflicts / tx
0.73
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,816,358 · 22 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
1w03w05w17w19w010w111w212w313w414w515w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf167f2da…09a4
0x34b655…2a6f
10 touches
10 conflicts
0xbdd97c21…e3d0
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x72083f0d…082a
0x34b655…2a6f
6 touches
3 conflicts
0xe098738f…9bbe
0x34b655…2a6f
6 touches
3 conflicts
0xb6039eff…b0d1
0x34b655…2a6f
6 touches
3 conflicts
0xf3453f63…d5ad
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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
10 conflicts on slot 0xf167f2da32…0e09a4
Audit this contract →
← previous block·next block →recent activity