← previous blocknext block →recent activity
Analyzing
Block #106,934,811
26 transactions · 25 stateful · 2026-09-22 04:02:57 UTC
Parallelism
65/100
Blocked
56%
Avg conflicts / tx
1.65
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,934,811 · 26 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
1w02w13w04w15w06w18w09w110w011w112w213w314w415w516w617w718w822w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xccebf5c5…8758
0x34b655…2a6f
18 touches
36 conflicts
0x232b0b19…d946
0x34b655…2a6f
18 touches
36 conflicts
0x38f35688…f1af
0x34b655…2a6f
18 touches
36 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x00000000…0002
0x125f12…a50b
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
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
36 conflicts on slot 0xccebf5c5cb…c88758
Audit this contract →
← previous block·next block →recent activity