← previous blocknext block →recent activity
Analyzing
Block #106,188,568
22 transactions · 19 stateful · 2026-09-19 13:26:03 UTC
Parallelism
59/100
Blocked
58%
Avg conflicts / tx
1.14
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,188,568 · 22 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w26w07w39w412w513w614w715w820w721w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e4184c2…f064
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0x58e06bab…34d1
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
15 conflicts on slot 0x6e4184c2d7…96f064
Audit this contract →
← previous block·next block →recent activity