← previous blocknext block →recent activity
Analyzing
Block #106,216,182
23 transactions · 23 stateful · 2026-09-19 15:45:04 UTC
Parallelism
61/100
Blocked
43%
Avg conflicts / tx
1.17
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,216,182 · 23 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w28w014w115w216w317w418w519w620w721w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7039b016…1ab2
0x34b655…2a6f
10 touches
10 conflicts
0x76ed8777…1e5f
0x34b655…2a6f
8 touches
6 conflicts
0xa3916e32…83b8
0x34b655…2a6f
8 touches
6 conflicts
0x2e90dcf9…1289
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0xe22ab637…7a8e
0x34b655…2a6f
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
10 conflicts on slot 0x7039b016be…9c1ab2
Audit this contract →
← previous block·next block →recent activity