← previous blocknext block →recent activity
Analyzing
Block #101,925,986
33 transactions · 30 stateful · 2026-09-04 14:36:29 UTC
Parallelism
85/100
Blocked
40%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,925,986 · 33 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
1w02w13w04w05w16w09w210w011w112w114w115w216w219w220w230w031w332w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0x2d3f3a3d…417f
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0x0a6cb118…4ca4
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x082a85db…aade
0x34b655…2a6f
4 touches
1 conflict
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 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity