← previous blocknext block →recent activity
Analyzing
Block #105,856,400
26 transactions · 25 stateful · 2026-09-18 09:33:17 UTC
Parallelism
69/100
Blocked
48%
Avg conflicts / tx
1.15
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,856,400 · 26 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
1w02w14w111w113w214w315w416w517w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x97e4c862…4419
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x5d4a7696…13d9
0x34b655…2a6f
8 touches
6 conflicts
0xd911522b…e960
0x34b655…2a6f
8 touches
6 conflicts
0x7c843949…1aa1
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
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
21 conflicts on slot 0x97e4c86258…af4419
Audit this contract →
← previous block·next block →recent activity