← previous blocknext block →recent activity
Analyzing
Block #106,252,335
22 transactions · 22 stateful · 2026-09-19 18:47:05 UTC
Parallelism
73/100
Blocked
59%
Avg conflicts / tx
1.41
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,252,335 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w25w06w27w310w311w412w413w518w520w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x12c3cd4d…b99f
0x34b655…2a6f
10 touches
10 conflicts
0x9fe14cdc…05ef
0x34b655…2a6f
8 touches
6 conflicts
0xa35509fa…5cb3
0x34b655…2a6f
8 touches
6 conflicts
0x219bfe67…87ae
0x34b655…2a6f
8 touches
6 conflicts
0x3e6302c8…64f5
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x5b6af007…0f35
0x34b655…2a6f
8 touches
6 conflicts
0x83522595…9b28
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0x12c3cd4d69…89b99f
Audit this contract →
← previous block·next block →recent activity