← previous blocknext block →recent activity
Analyzing
Block #101,993,121
28 transactions · 24 stateful · 2026-09-04 20:17:05 UTC
Parallelism
71/100
Blocked
58%
Avg conflicts / tx
1.14
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #101,993,121 · 28 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w17w28w39w414w422w327w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d616e7c…a6a1
0x34b655…2a6f
10 touches
10 conflicts
0xb73a5ffd…ddee
0x34b655…2a6f
10 touches
10 conflicts
0xc0f6895c…e428
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
10 touches
10 conflicts
0xe0da07e4…ccf2
0x34b655…2a6f
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x2aa7be4c…0f84
0x34b655…2a6f
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
10 conflicts on slot 0x8d616e7c6c…98a6a1
Audit this contract →
← previous block·next block →recent activity