← previous blocknext block →recent activity
Analyzing
Block #105,880,455
19 transactions · 18 stateful · 2026-09-18 11:34:20 UTC
Parallelism
58/100
Blocked
44%
Avg conflicts / tx
1.32
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,880,455 · 19 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
5w06w17w29w310w411w512w613w714w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xacd7220d…e389
0x34b655…2a6f
14 touches
21 conflicts
0x203d3e2c…fa40
0x34b655…2a6f
10 touches
10 conflicts
0x5fad6fee…7714
0x34b655…2a6f
10 touches
10 conflicts
0xf788c790…e66f
0x34b655…2a6f
10 touches
10 conflicts
0x97e4c862…4419
0x34b655…2a6f
8 touches
6 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xfefb0189…f726
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 0xacd7220d5f…58e389
Audit this contract →
← previous block·next block →recent activity