← previous blocknext block →recent activity
Analyzing
Block #110,393,519
22 transactions · 19 stateful · 2026-10-04 06:21:29 UTC
Parallelism
77/100
Blocked
47%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #110,393,519 · 22 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
1w02w14w28w09w112w013w115w116w217w318w421w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0bf5bdc2…92c9
0x34b655…2a6f
10 touches
10 conflicts
0xe9457301…83cd
0x34b655…2a6f
8 touches
6 conflicts
0xdf64e5e6…75e8
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x77762137…2893
0x34b655…2a6f
4 touches
1 conflict
0x8a2657f5…e008
0x34b655…2a6f
4 touches
1 conflict
0x93269085…a48f
0x34b655…2a6f
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
10 conflicts on slot 0x0bf5bdc215…fb92c9
Audit this contract →
← previous block·next block →recent activity