← previous blocknext block →recent activity
Analyzing
Block #90,804,358
13 transactions · 13 stateful · 2026-07-27 15:12:43 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,804,358 · 13 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
1w02w13w24w08w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x75d35778…73c5
0x34b655…2a6f
4 touches
1 conflict
0xc4ca986e…4e06
0x34b655…2a6f
4 touches
1 conflict
0x17a5bb2a…4271
0x34b655…2a6f
2 touches
0 conflicts
0x23c9c7bf…4e33
0x34b655…2a6f
2 touches
0 conflicts
0x23e3c7fa…5f09
0x34b655…2a6f
2 touches
0 conflicts
0x262d4253…b091
0x34b655…2a6f
2 touches
0 conflicts
0x3a15f0fa…d60a
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity