← previous blocknext block →recent activity
Analyzing
Block #106,207,808
18 transactions · 16 stateful · 2026-09-19 15:02:56 UTC
Parallelism
56/100
Blocked
44%
Avg conflicts / tx
1.56
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,207,808 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w212w314w415w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb808cfd…e52a
0x34b655…2a6f
12 touches
15 conflicts
0x3bb4ea6a…2370
0x34b655…2a6f
12 touches
15 conflicts
0xaef82336…d052
0x34b655…2a6f
10 touches
10 conflicts
0x742436a7…c4d4
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x206f4379…e08a
0x34b655…2a6f
6 touches
3 conflicts
0xd597209e…9800
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
15 conflicts on slot 0xbb808cfd89…29e52a
Audit this contract →
← previous block·next block →recent activity