← previous blocknext block →recent activity
Analyzing
Block #106,185,656
21 transactions · 20 stateful · 2026-09-19 13:11:24 UTC
Parallelism
62/100
Blocked
70%
Avg conflicts / tx
2.19
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,185,656 · 21 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
1w02w13w24w35w06w17w18w29w211w312w313w414w515w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42260953…76b3
0x34b655…2a6f
16 touches
28 conflicts
0xd0fef1eb…9fc2
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…001e
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002e
0x1b6862…e19c
8 touches
6 conflicts
0x90d24713…b88e
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
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
28 conflicts on slot 0x4226095336…1b76b3
Audit this contract →
← previous block·next block →recent activity