← previous blocknext block →recent activity
Analyzing
Block #106,370,218
25 transactions · 24 stateful · 2026-09-20 04:40:17 UTC
Parallelism
64/100
Blocked
54%
Avg conflicts / tx
1.8
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,370,218 · 25 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w19w210w315w216w317w420w521w622w723w824w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76aac745…357d
0x34b655…2a6f
16 touches
28 conflicts
0x7462b8f2…6312
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x89eaf36a…4e48
0x34b655…2a6f
10 touches
10 conflicts
0xdd77da90…6df4
0x34b655…2a6f
8 touches
6 conflicts
0x5bfab785…f2b5
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x234291b8…3698
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
28 conflicts on slot 0x76aac74552…f2357d
Audit this contract →
← previous block·next block →recent activity