← previous blocknext block →recent activity
Analyzing
Block #91,432,585
16 transactions · 15 stateful · 2026-07-29 19:56:28 UTC
Parallelism
69/100
Blocked
67%
Avg conflicts / tx
1.19
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,432,585 · 16 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
1w02w13w24w15w06w17w08w19w310w211w312w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0672e4a2…8d1f
0x34b655…2a6f
8 touches
6 conflicts
0x6b8f0411…51e5
0xd32edf…ff58
7 touches
6 conflicts
0xda2ee2e7…968a
0x34b655…2a6f
6 touches
3 conflicts
0x0d260b15…aa11
0x34b655…2a6f
4 touches
1 conflict
0x11e60d91…a467
0x34b655…2a6f
4 touches
1 conflict
0x12df41b1…d03c
0x34b655…2a6f
4 touches
1 conflict
0x1c3295fd…097a
0x34b655…2a6f
4 touches
1 conflict
0x22c64700…84b1
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
6 conflicts on slot 0x0672e4a279…2f8d1f
Audit this contract →
← previous block·next block →recent activity