← previous blocknext block →recent activity
Analyzing
Block #105,683,818
31 transactions · 21 stateful · 2026-09-17 19:03:16 UTC
Parallelism
81/100
Blocked
43%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,683,818 · 31 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
1w03w14w26w07w18w011w112w224w326w427w328w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc08384da…ecb7
0x34b655…2a6f
8 touches
6 conflicts
0xf6dfaa05…2749
0x34b655…2a6f
8 touches
6 conflicts
0xa7013be2…c0a8
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x199a4f01…2183
0x34b655…2a6f
6 touches
3 conflicts
0x1eb0fab5…3517
0x34b655…2a6f
6 touches
3 conflicts
0x366a19b0…f065
0x34b655…2a6f
6 touches
3 conflicts
0x4e9b892b…6877
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
6 conflicts on slot 0xc08384da3a…ebecb7
Audit this contract →
← previous block·next block →recent activity