← previous blocknext block →recent activity
Analyzing
Block #106,916,905
23 transactions · 21 stateful · 2026-09-22 02:32:49 UTC
Parallelism
78/100
Blocked
52%
Avg conflicts / tx
1.09
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,916,905 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w16w27w38w09w110w211w312w413w115w217w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba1edffb…323e
0x34b655…2a6f
10 touches
10 conflicts
0xccebf5c5…8758
0x34b655…2a6f
10 touches
10 conflicts
0xf7ae2120…d1d2
0x34b655…2a6f
10 touches
10 conflicts
0x69411fb3…e36d
0x34b655…2a6f
10 touches
10 conflicts
0x3a0218bf…e2a3
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xc0f29314…17fc
0x1b6862…e19c
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
10 conflicts on slot 0xba1edffb42…64323e
Audit this contract →
← previous block·next block →recent activity