← previous blocknext block →recent activity
Analyzing
Block #105,930,962
23 transactions · 20 stateful · 2026-09-18 15:49:26 UTC
Parallelism
65/100
Blocked
55%
Avg conflicts / tx
1.43
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,930,962 · 23 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
1w03w14w06w210w311w412w313w515w416w517w618w722w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb11940a…519b
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xbff5186e…dfb3
0x34b655…2a6f
6 touches
3 conflicts
0xad99b1fd…1c5a
0x34b655…2a6f
6 touches
3 conflicts
0xbc8fb280…76a3
0x34b655…2a6f
4 touches
1 conflict
0xd29e547b…a1dd
0x34b655…2a6f
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 0xdb11940a1f…24519b
Audit this contract →
← previous block·next block →recent activity