← previous blocknext block →recent activity
Analyzing
Block #105,920,956
22 transactions · 18 stateful · 2026-09-18 14:59:03 UTC
Parallelism
73/100
Blocked
39%
Avg conflicts / tx
0.64
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,920,956 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w26w313w415w117w218w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x50de0015…275c
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x20b1228b…2487
0x34b655…2a6f
6 touches
3 conflicts
0x110a3804…f842
0x34b655…2a6f
4 touches
1 conflict
0x3018a378…d7bb
0x34b655…2a6f
4 touches
1 conflict
0x315e07b8…9823
0x34b655…2a6f
4 touches
1 conflict
0x34836ffb…2a0b
0x34b655…2a6f
4 touches
1 conflict
0x377ea90e…e6c2
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
6 conflicts on slot 0x50de001558…88275c
Audit this contract →
← previous block·next block →recent activity