← previous blocknext block →recent activity
Analyzing
Block #106,935,334
28 transactions · 27 stateful · 2026-09-22 04:05:35 UTC
Parallelism
75/100
Blocked
63%
Avg conflicts / tx
1.29
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,935,334 · 28 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
2w03w14w05w16w17w08w19w210w211w312w413w514w616w217w320w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc8c615d4…5da3
0x34b655…2a6f
12 touches
15 conflicts
0xae2b2871…1692
0x34b655…2a6f
10 touches
10 conflicts
0xccebf5c5…8758
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0x874cb67f…26df
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
15 conflicts on slot 0xc8c615d41e…025da3
Audit this contract →
← previous block·next block →recent activity