← previous blocknext block →recent activity
Analyzing
Block #112,489,611
77 transactions · 65 stateful · 2026-10-11 14:13:59 UTC
Parallelism
70/100
Blocked
72%
Avg conflicts / tx
3.7
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #112,489,611 · 77 txs across 23 waves · depth 23
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
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
wave w21
wave w22
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w17w210w314w117w418w541w443w645w546w647w648w749w750w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
38 touches
171 conflicts
0x00000000…0002
0x125f12…a50b
16 touches
28 conflicts
0x35a74ab3…0fac
0xd32edf…ff58
13 touches
21 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
12 touches
15 conflicts
0xccebf5c5…8758
0x34b655…2a6f
12 touches
15 conflicts
0xcb45d9d6…cb84
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002c
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
171 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity