← previous blocknext block →recent activity
Analyzing
Block #110,386,104
25 transactions · 20 stateful · 2026-10-04 05:44:10 UTC
Parallelism
52/100
Blocked
60%
Avg conflicts / tx
2.04
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #110,386,104 · 25 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w36w47w58w612w716w818w120w923w1024w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1c4e5ce…0dec
0x34b655…2a6f
16 touches
28 conflicts
0x9abad0e8…28a3
0x34b655…2a6f
14 touches
21 conflicts
0xb6b7c702…5cdf
0xd32edf…ff58
13 touches
21 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
0x203caab3…21bf
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 0xe1c4e5ce15…770dec
Audit this contract →
← previous block·next block →recent activity