← previous blocknext block →recent activity
Analyzing
Block #106,386,096
24 transactions · 24 stateful · 2026-09-20 06:00:12 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
1.67
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,386,096 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w28w311w412w314w216w417w518w619w722w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xabd5acc1…22cb
0x34b655…2a6f
16 touches
28 conflicts
0xcd9ba26b…108d
0x34b655…2a6f
10 touches
10 conflicts
0x0dd3d3cd…7281
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x310a7246…2dcb
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
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
28 conflicts on slot 0xabd5acc150…6922cb
Audit this contract →
← previous block·next block →recent activity