← previous blocknext block →recent activity
Analyzing
Block #106,537,685
20 transactions · 19 stateful · 2026-09-20 18:43:10 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
1.3
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,537,685 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w39w110w211w312w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x675fa4ed…02bf
0x34b655…2a6f
10 touches
10 conflicts
0xa35509fa…5cb3
0x34b655…2a6f
8 touches
6 conflicts
0x3af041d1…6f61
0x34b655…2a6f
8 touches
6 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
6 touches
3 conflicts
0x8d47c9a4…f11f
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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 0x675fa4ed4b…fe02bf
Audit this contract →
← previous block·next block →recent activity