← previous blocknext block →recent activity
Analyzing
Block #101,988,563
18 transactions · 16 stateful · 2026-09-04 19:53:57 UTC
Parallelism
72/100
Blocked
56%
Avg conflicts / tx
0.89
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,988,563 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w08w111w212w215w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x045532dd…4b7d
0x34b655…2a6f
6 touches
3 conflicts
0x04d4f30d…4dfb
0x34b655…2a6f
6 touches
3 conflicts
0x3e7ad612…e804
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x55a44c85…e548
0x34b655…2a6f
6 touches
3 conflicts
0x5746581b…0cb1
0x34b655…2a6f
6 touches
3 conflicts
0x61a11641…fef0
0x34b655…2a6f
6 touches
3 conflicts
0x65903ef9…2567
0x34b655…2a6f
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
3 conflicts on slot 0x045532dd4b…244b7d
Audit this contract →
← previous block·next block →recent activity