← previous blocknext block →recent activity
Analyzing
Block #106,809,988
32 transactions · 24 stateful · 2026-09-21 17:34:40 UTC
Parallelism
78/100
Blocked
46%
Avg conflicts / tx
0.72
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,809,988 · 32 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
1w06w07w08w19w210w311w115w121w122w424w225w528w630w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x186dd464…0f77
0x34b655…2a6f
8 touches
6 conflicts
0x24b2ba87…21ff
0x34b655…2a6f
8 touches
6 conflicts
0xbe4d01fe…6754
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…001b
0x1b6862…e19c
6 touches
3 conflicts
0xcb45d9d6…cb83
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0012
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
6 conflicts on slot 0x186dd4644e…d90f77
Audit this contract →
← previous block·next block →recent activity