← previous blocknext block →recent activity
Analyzing
Block #106,235,646
24 transactions · 23 stateful · 2026-09-19 17:23:05 UTC
Parallelism
71/100
Blocked
52%
Avg conflicts / tx
1.54
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,235,646 · 24 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
1w02w03w06w17w28w111w012w313w414w515w516w620w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x85332e39…0222
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x1e28635a…ba38
0x34b655…2a6f
8 touches
6 conflicts
0xa35509fa…5cb3
0x34b655…2a6f
6 touches
3 conflicts
0x2c2db8e9…fdc7
0x34b655…2a6f
6 touches
3 conflicts
0x4786839b…c29a
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
10 conflicts on slot 0x85332e39ec…770222
Audit this contract →
← previous block·next block →recent activity