← previous blocknext block →recent activity
Analyzing
Block #105,619,726
22 transactions · 21 stateful · 2026-09-17 13:40:38 UTC
Parallelism
64/100
Blocked
48%
Avg conflicts / tx
1.64
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,619,726 · 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
1w02w03w14w25w36w47w59w115w618w719w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda976e7f…128a
0x34b655…2a6f
16 touches
28 conflicts
0x7d0eaae2…60b7
0x34b655…2a6f
8 touches
6 conflicts
0x5fde4971…aac9
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x59bb7f38…13a3
0x34b655…2a6f
8 touches
6 conflicts
0x3bad46c2…b842
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x99219c43…3f68
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 0xda976e7f2f…0e128a
Audit this contract →
← previous block·next block →recent activity