← previous blocknext block →recent activity
Analyzing
Block #105,869,077
20 transactions · 18 stateful · 2026-09-18 10:37:05 UTC
Parallelism
80/100
Blocked
50%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,869,077 · 20 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
1w02w13w24w35w06w07w19w010w111w213w014w115w217w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d482678…febe
0x34b655…2a6f
8 touches
6 conflicts
0x6caf33e2…c261
0x34b655…2a6f
8 touches
6 conflicts
0x4abfb389…18f4
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x18978822…2623
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x42522e76…2592
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 0x6d48267899…e3febe
Audit this contract →
← previous block·next block →recent activity