← previous blocknext block →recent activity
Analyzing
Block #110,220,531
20 transactions · 20 stateful · 2026-10-03 15:51:07 UTC
Parallelism
75/100
Blocked
30%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #110,220,531 · 20 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
8w09w110w215w016w117w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x7954ece9…fef0
0x34b655…2a6f
6 touches
3 conflicts
0xfdd40e24…dca0
0x34b655…2a6f
6 touches
3 conflicts
0xccebf5c5…8758
0x34b655…2a6f
4 touches
1 conflict
0x31a338d0…ed1e
0x34b655…2a6f
4 touches
1 conflict
0x9d1c9a2f…4431
0x34b655…2a6f
4 touches
1 conflict
0x96ea3b16…d4dc
0x34b655…2a6f
3 touches
1 conflict
0x4dc8c6f0…dd57
0x34b655…2a6f
3 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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity