← previous blocknext block →recent activity
Analyzing
Block #106,393,337
30 transactions · 29 stateful · 2026-09-20 06:36:39 UTC
Parallelism
63/100
Blocked
55%
Avg conflicts / tx
1.87
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,393,337 · 30 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w27w311w413w518w621w523w724w825w926w1029w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe32e848a…851e
0x34b655…2a6f
18 touches
36 conflicts
0x5d1ac445…5233
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x8d175439…fb79
0x34b655…2a6f
8 touches
6 conflicts
0x0dd3d3cd…7281
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x3af0dd8e…0023
0x1b6862…e19c
8 touches
6 conflicts
0x49b9fdd5…9c16
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
36 conflicts on slot 0xe32e848a30…f2851e
Audit this contract →
← previous block·next block →recent activity