← previous blocknext block →recent activity
Analyzing
Block #101,991,132
31 transactions · 27 stateful · 2026-09-04 20:07:01 UTC
Parallelism
65/100
Blocked
59%
Avg conflicts / tx
1.61
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #101,991,132 · 31 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
1w02w13w24w35w48w09w110w213w521w223w625w726w827w728w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x045532dd…4b7d
0x34b655…2a6f
12 touches
15 conflicts
0x51fc8795…126f
0x34b655…2a6f
12 touches
15 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
0xac79a0c7…be11
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
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
15 conflicts on slot 0x045532dd4b…244b7d
Audit this contract →
← previous block·next block →recent activity