← previous blocknext block →recent activity
Analyzing
Block #106,215,248
27 transactions · 25 stateful · 2026-09-19 15:40:22 UTC
Parallelism
74/100
Blocked
68%
Avg conflicts / tx
1.78
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,215,248 · 27 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
1w02w13w24w05w16w27w28w39w410w219w420w521w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb36f9b2f…d49a
0x34b655…2a6f
12 touches
15 conflicts
0x1a84e266…4f8a
0x34b655…2a6f
10 touches
10 conflicts
0xe098738f…9bbe
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0x23a320fb…cbd7
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
10 touches
10 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0x80398c66…f3cc
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
15 conflicts on slot 0xb36f9b2f6c…b1d49a
Audit this contract →
← previous block·next block →recent activity