← previous blocknext block →recent activity
Analyzing
Block #105,460,978
23 transactions · 18 stateful · 2026-09-17 00:21:40 UTC
Parallelism
74/100
Blocked
39%
Avg conflicts / tx
0.61
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,460,978 · 23 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
1w04w15w06w112w215w316w417w519w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d0eaae2…60b7
0x34b655…2a6f
8 touches
6 conflicts
0x0b07ebc8…a3d8
0x34b655…2a6f
6 touches
3 conflicts
0x81ca8c9e…28cb
0x34b655…2a6f
6 touches
3 conflicts
0x90a021f0…f922
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x25b2a901…bace
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x178a61ad…4958
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 0x7d0eaae22e…4260b7
Audit this contract →
← previous block·next block →recent activity