← previous blocknext block →recent activity
Analyzing
Block #91,127,762
20 transactions · 19 stateful · 2026-07-28 18:20:41 UTC
Parallelism
85/100
Blocked
21%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,127,762 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w09w111w213w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49887f7e…9e7c
0x34b655…2a6f
6 touches
3 conflicts
0xbe9baf16…df37
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x299c0f04…09cf
0x34b655…2a6f
4 touches
1 conflict
0x46f18754…18b3
0x34b655…2a6f
4 touches
1 conflict
0x4a80672e…d008
0x34b655…2a6f
4 touches
1 conflict
0x4e58deff…c5d0
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 0x49887f7ea5…989e7c
Audit this contract →
← previous block·next block →recent activity