← previous blocknext block →recent activity
Analyzing
Block #101,838,216
17 transactions · 15 stateful · 2026-09-04 07:13:33 UTC
Parallelism
71/100
Blocked
60%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,838,216 · 17 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
1w02w13w24w35w49w212w113w215w216w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67c1f465…38b3
0x34b655…2a6f
6 touches
3 conflicts
0x7746704d…9928
0x34b655…2a6f
6 touches
3 conflicts
0x7810c784…070c
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x02372d42…1871
0x34b655…2a6f
6 touches
3 conflicts
0xf36124ad…c08f
0x34b655…2a6f
6 touches
3 conflicts
0x53e08444…d671
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 0x67c1f46537…4d38b3
Audit this contract →
← previous block·next block →recent activity