← previous blocknext block →recent activity
Analyzing
Block #105,852,479
22 transactions · 20 stateful · 2026-09-18 09:13:32 UTC
Parallelism
64/100
Blocked
45%
Avg conflicts / tx
1.36
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,852,479 · 22 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
1w03w010w111w112w213w314w415w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x12c00063…cb00
0x34b655…2a6f
16 touches
28 conflicts
0x36557a79…cf09
0x34b655…2a6f
12 touches
15 conflicts
0x5b6af007…0f35
0x34b655…2a6f
12 touches
15 conflicts
0x18978822…2623
0x34b655…2a6f
10 touches
10 conflicts
0x206f4379…e08a
0x34b655…2a6f
10 touches
10 conflicts
0x8c6d6fd6…f74b
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
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
28 conflicts on slot 0x12c00063ba…68cb00
Audit this contract →
← previous block·next block →recent activity