← previous blocknext block →recent activity
Analyzing
Block #110,386,536
21 transactions · 20 stateful · 2026-10-04 05:46:21 UTC
Parallelism
33/100
Blocked
70%
Avg conflicts / tx
2.86
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #110,386,536 · 21 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w713w714w815w917w1019w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9abad0e8…28a3
0x34b655…2a6f
16 touches
28 conflicts
0x64606160…3b1c
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001a
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002a
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0040
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0053
0x1b6862…e19c
10 touches
10 conflicts
0x37009e5f…aa44
0x1b6862…e19c
10 touches
10 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
28 conflicts on slot 0x9abad0e8ca…8028a3
Audit this contract →
← previous block·next block →recent activity