← previous blocknext block →recent activity
Analyzing
Block #110,321,910
15 transactions · 13 stateful · 2026-10-04 00:21:12 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #110,321,910 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w29w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xfdd40e24…dca0
0x34b655…2a6f
4 touches
1 conflict
0x3156f31b…b402
0x34b655…2a6f
4 touches
1 conflict
0xce07ade3…0bfa
0x34b655…2a6f
4 touches
1 conflict
0xce7a3604…c4b6
0x34b655…2a6f
4 touches
1 conflict
0x7954ece9…fef0
0x34b655…2a6f
4 touches
1 conflict
0x49caf158…7d90
0x34b655…2a6f
2 touches
0 conflicts
0xccebf5c5…8758
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity