← previous blocknext block →recent activity
Analyzing
Block #107,813,263
22 transactions · 22 stateful · 2026-09-25 05:46:59 UTC
Parallelism
50/100
Blocked
59%
Avg conflicts / tx
2
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #107,813,263 · 22 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w17w08w19w210w311w412w513w614w715w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba522812…1f1f
0x34b655…2a6f
14 touches
21 conflicts
0x3aff72dc…a704
0x34b655…2a6f
14 touches
21 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0xc64d3656…0c1c
0x34b655…2a6f
10 touches
10 conflicts
0x429c8b35…0f5c
0x34b655…2a6f
10 touches
10 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
8 touches
6 conflicts
0x34a6145f…b17d
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0xba52281226…3a1f1f
Audit this contract →
← previous block·next block →recent activity