← previous blocknext block →recent activity
Analyzing
Block #106,786,417
34 transactions · 28 stateful · 2026-09-21 15:36:00 UTC
Parallelism
76/100
Blocked
57%
Avg conflicts / tx
1.18
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,786,417 · 34 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
2w03w04w05w06w17w111w112w217w318w119w121w123w424w525w626w731w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x518221db…65f7
0x34b655…2a6f
16 touches
28 conflicts
0x72055cb1…12e9
0x34b655…2a6f
12 touches
15 conflicts
0xe098738f…9bbe
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x4abfb389…18f4
0x34b655…2a6f
6 touches
3 conflicts
0x69411fb3…e36d
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
28 conflicts on slot 0x518221db7f…5465f7
Audit this contract →
← previous block·next block →recent activity