← previous blocknext block →recent activity
Analyzing
Block #101,024,810
31 transactions · 24 stateful · 2026-09-01 11:01:07 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1.06
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #101,024,810 · 31 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w317w420w124w425w526w627w728w829w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x51fc8795…126f
0x34b655…2a6f
10 touches
10 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
10 touches
10 conflicts
0x25952275…f5e6
0xd32edf…ff58
9 touches
10 conflicts
0x7dd96c96…7335
0x34b655…2a6f
8 touches
6 conflicts
0x336486a4…20bd
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity