← previous blocknext block →recent activity
Analyzing
Block #111,060,494
25 transactions · 23 stateful · 2026-10-06 14:21:37 UTC
Parallelism
56/100
Blocked
65%
Avg conflicts / tx
1.96
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #111,060,494 · 25 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w36w48w010w112w313w217w318w419w520w621w722w823w924w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x5280717c…5e52
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0018
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0028
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0040
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0051
0x1b6862…e19c
8 touches
6 conflicts
0x411a01cc…e442
0x1b6862…e19c
8 touches
6 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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity