← previous blocknext block →recent activity
Analyzing
Block #90,794,792
10 transactions · 10 stateful · 2026-07-27 14:24:35 UTC
Parallelism
70/100
Blocked
30%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,794,792 · 10 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
1w02w13w26w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x0a57a2b8…3cdd
0x34b655…2a6f
4 touches
1 conflict
0x1ebb35bb…ef2a
0x34b655…2a6f
4 touches
1 conflict
0x0725ad1d…a03f
0x34b655…2a6f
2 touches
0 conflicts
0x0d300dde…4f32
0x34b655…2a6f
2 touches
0 conflicts
0x107b89e4…470d
0x34b655…2a6f
2 touches
0 conflicts
0x1aa62c36…420a
0x34b655…2a6f
2 touches
0 conflicts
0x24b6091e…d294
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