← previous blocknext block →recent activity
Analyzing
Block #106,155,117
23 transactions · 23 stateful · 2026-09-19 10:37:42 UTC
Parallelism
70/100
Blocked
52%
Avg conflicts / tx
1.35
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,155,117 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w09w211w312w413w514w215w322w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd41f5136…97c6
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xf2acfba1…5e29
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0x675fa4ed…02bf
0x34b655…2a6f
6 touches
3 conflicts
0xaa3b4402…74e6
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
15 conflicts on slot 0xd41f513688…4197c6
Audit this contract →
← previous block·next block →recent activity