← previous blocknext block →recent activity
Analyzing
Block #105,855,763
26 transactions · 23 stateful · 2026-09-18 09:30:04 UTC
Parallelism
77/100
Blocked
30%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,855,763 · 26 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
2w05w06w17w215w216w317w418w519w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4dc3591…b669
0x34b655…2a6f
10 touches
10 conflicts
0x43e3decb…be40
0x34b655…2a6f
10 touches
10 conflicts
0x02dec2a1…1f44
0x34b655…2a6f
10 touches
10 conflicts
0xd6d040d9…9ae3
0x34b655…2a6f
6 touches
3 conflicts
0x18978822…2623
0x34b655…2a6f
6 touches
3 conflicts
0x0efc210e…70ab
0x34b655…2a6f
6 touches
3 conflicts
0xf8e6479f…f193
0x34b655…2a6f
6 touches
3 conflicts
0xf2bbd8fc…7e49
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
10 conflicts on slot 0xb4dc35918f…85b669
Audit this contract →
← previous block·next block →recent activity