← previous blocknext block →recent activity
Analyzing
Block #110,392,765
25 transactions · 20 stateful · 2026-10-04 06:17:41 UTC
Parallelism
84/100
Blocked
30%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #110,392,765 · 25 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
1w02w14w05w16w27w321w323w024w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7954ece9…fef0
0x34b655…2a6f
8 touches
6 conflicts
0xfdd40e24…dca0
0x34b655…2a6f
8 touches
6 conflicts
0x6432b7bf…660c
0x34b655…2a6f
6 touches
3 conflicts
0xccebf5c5…8758
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0040
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0053
0x1b6862…e19c
4 touches
1 conflict
0x038d4614…c672
0x1b6862…e19c
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 0x7954ece9af…e7fef0
Audit this contract →
← previous block·next block →recent activity