← previous blocknext block →recent activity
Analyzing
Block #106,380,593
28 transactions · 27 stateful · 2026-09-20 05:32:31 UTC
Parallelism
68/100
Blocked
67%
Avg conflicts / tx
2.07
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,380,593 · 28 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
1w02w13w24w35w46w07w18w113w215w216w317w418w221w522w623w724w826w127w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaa35a811…8c66
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
10 touches
10 conflicts
0xf58e0252…01f6
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0x84611dd3…b343
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
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 0xaa35a811c2…a58c66
Audit this contract →
← previous block·next block →recent activity