← previous blocknext block →recent activity
Analyzing
Block #107,813,306
21 transactions · 21 stateful · 2026-09-25 05:47:11 UTC
Parallelism
52/100
Blocked
57%
Avg conflicts / tx
1.76
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #107,813,306 · 21 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w08w19w210w311w412w513w614w715w816w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa0cbbfcc…3133
0x34b655…2a6f
12 touches
15 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0xba522812…1f1f
0x34b655…2a6f
10 touches
10 conflicts
0x9ca6fa7b…aeb3
0x34b655…2a6f
8 touches
6 conflicts
0x48203298…65cb
0x34b655…2a6f
8 touches
6 conflicts
0x2b76a1fb…fdfc
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
15 conflicts on slot 0xa0cbbfcc1a…1b3133
Audit this contract →
← previous block·next block →recent activity