← previous blocknext block →recent activity
Analyzing
Block #110,308,233
34 transactions · 30 stateful · 2026-10-03 23:12:23 UTC
Parallelism
91/100
Blocked
13%
Avg conflicts / tx
0.15
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #110,308,233 · 34 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ab23153…8f44
0x34b655…2a6f
6 touches
3 conflicts
0xb4656137…5858
0x34b655…2a6f
6 touches
3 conflicts
0x8c211514…b757
0x34b655…2a6f
6 touches
3 conflicts
0x7e67e15b…4aa7
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0xe720a4c6…8eb0
0x34b655…2a6f
4 touches
1 conflict
0xcbbc3148…18b0
0x80ef19…40df
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
3 conflicts on slot 0x4ab23153bc…fb8f44
Audit this contract →
← previous block·next block →recent activity