← previous blocknext block →recent activity
Analyzing
Block #105,842,291
37 transactions · 34 stateful · 2026-09-18 08:22:08 UTC
Parallelism
78/100
Blocked
59%
Avg conflicts / tx
1.32
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,842,291 · 37 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
1w02w13w24w35w411w413w016w117w018w119w220w321w122w423w524w633w134w536w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x289ac5ba…93c8
0x34b655…2a6f
12 touches
15 conflicts
0xd1448207…452d
0x34b655…2a6f
10 touches
10 conflicts
0xcd5c0ecb…4b5f
0x34b655…2a6f
10 touches
10 conflicts
0x81ffdee4…9a1e
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0x1f8a126c…9aa8
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
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
15 conflicts on slot 0x289ac5ba2f…f393c8
Audit this contract →
← previous block·next block →recent activity