← previous blocknext block →recent activity
Analyzing
Block #110,328,891
13 transactions · 13 stateful · 2026-10-04 00:56:20 UTC
Parallelism
85/100
Blocked
15%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #110,328,891 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf1d83bb1…f3a8
0x34b655…2a6f
4 touches
1 conflict
0xfdd40e24…dca0
0x34b655…2a6f
4 touches
1 conflict
0xce7a3604…c4b6
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x7954ece9…fef0
0x34b655…2a6f
4 touches
1 conflict
0x6e204c9d…fa1d
0x34b655…2a6f
2 touches
0 conflicts
0x842449ec…ded1
0x34b655…2a6f
2 touches
0 conflicts
0x8b0143a9…ba7b
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xf1d83bb142…46f3a8
Audit this contract →
← previous block·next block →recent activity