← previous blocknext block →recent activity
Analyzing
Block #101,988,900
18 transactions · 18 stateful · 2026-09-04 19:55:39 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,988,900 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w112w013w414w516w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf7772b49…fc12
0x34b655…2a6f
8 touches
6 conflicts
0x02372d42…1871
0x34b655…2a6f
8 touches
6 conflicts
0x3e7ad612…e804
0x34b655…2a6f
8 touches
6 conflicts
0x53e08444…d671
0x34b655…2a6f
8 touches
6 conflicts
0x6823c28e…594c
0x34b655…2a6f
8 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0xc0f6895c…e428
0x34b655…2a6f
8 touches
6 conflicts
0xcd4c444f…b28a
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
6 conflicts on slot 0xf7772b4910…d2fc12
Audit this contract →
← previous block·next block →recent activity