← previous blocknext block →recent activity
Analyzing
Block #91,074,707
26 transactions · 20 stateful · 2026-07-28 13:53:42 UTC
Parallelism
85/100
Blocked
45%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,074,707 · 26 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w08w19w010w111w214w015w118w221w222w323w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x0817711c…bf1f
0x34b655…2a6f
4 touches
1 conflict
0x08a39015…efa0
0x34b655…2a6f
4 touches
1 conflict
0x15c22181…1354
0x34b655…2a6f
4 touches
1 conflict
0x301e1c77…9e30
0x34b655…2a6f
4 touches
1 conflict
0x3c78ca04…432c
0x34b655…2a6f
4 touches
1 conflict
0x4acbdbcf…a8c6
0x34b655…2a6f
4 touches
1 conflict
0x5376f5ee…5daa
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity