← previous blocknext block →recent activity
Analyzing
Block #106,215,176
28 transactions · 25 stateful · 2026-09-19 15:40:01 UTC
Parallelism
71/100
Blocked
56%
Avg conflicts / tx
1.36
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,215,176 · 28 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
1w02w13w24w35w46w58w011w012w113w219w624w126w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x94f4eab2…673c
0x34b655…2a6f
14 touches
21 conflicts
0x5e803aa6…bbd4
0x34b655…2a6f
12 touches
15 conflicts
0xd17580f9…ece1
0x754704…b603
10 touches
10 conflicts
0x85eb1316…bb9e
0x34b655…2a6f
8 touches
6 conflicts
0x23a320fb…cbd7
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x22891c92…012d
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0x94f4eab25f…91673c
Audit this contract →
← previous block·next block →recent activity