← previous blocknext block →recent activity
Analyzing
Block #105,845,059
22 transactions · 21 stateful · 2026-09-18 08:36:10 UTC
Parallelism
59/100
Blocked
43%
Avg conflicts / tx
1.32
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #105,845,059 · 22 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
2w03w15w010w111w213w314w415w516w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd7f5b55…4994
0x34b655…2a6f
14 touches
21 conflicts
0xf0a87843…7c8a
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x5e3014f0…b4e1
0x34b655…2a6f
8 touches
6 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x27a04273…27c5
0x065c9d…c394
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
21 conflicts on slot 0xfd7f5b557f…f74994
Audit this contract →
← previous block·next block →recent activity