← previous blocknext block →recent activity
Analyzing
Block #105,617,779
26 transactions · 25 stateful · 2026-09-17 13:30:50 UTC
Parallelism
85/100
Blocked
48%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,617,779 · 26 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w06w17w29w110w214w115w216w017w318w019w120w221w324w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd5c0ecb…4b5f
0x34b655…2a6f
6 touches
3 conflicts
0x6b595a5d…894c
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xfb2f615c…158e
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x7d0eaae2…60b7
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xf5b5f7…6d70
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
3 conflicts on slot 0xcd5c0ecbc1…2f4b5f
Audit this contract →
← previous block·next block →recent activity