← previous blocknext block →recent activity
Analyzing
Block #106,100,418
25 transactions · 24 stateful · 2026-09-19 06:02:25 UTC
Parallelism
80/100
Blocked
58%
Avg conflicts / tx
1.16
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,100,418 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w27w08w09w311w313w116w017w219w120w321w422w124w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1f1aef36…d977
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x735a86cd…b64d
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x932a9590…0b19
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x1f1aef36e2…6ed977
Audit this contract →
← previous block·next block →recent activity