← previous blocknext block →recent activity
Analyzing
Block #106,385,979
27 transactions · 26 stateful · 2026-09-20 05:59:37 UTC
Parallelism
70/100
Blocked
54%
Avg conflicts / tx
1.81
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,385,979 · 27 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
1w02w13w24w35w06w18w110w213w316w217w318w419w520w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x638b4c5d…0483
0x34b655…2a6f
16 touches
28 conflicts
0xcd9ba26b…108d
0x34b655…2a6f
12 touches
15 conflicts
0x038b9243…553d
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0xba5743c7…21c1
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
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 0x638b4c5d22…2d0483
Audit this contract →
← previous block·next block →recent activity