← previous blocknext block →recent activity
Analyzing
Block #90,791,652
18 transactions · 16 stateful · 2026-07-27 14:08:47 UTC
Parallelism
83/100
Blocked
19%
Avg conflicts / tx
0.17
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,791,652 · 18 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
1w04w05w16w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xa6b89ebb…a66e
0x34b655…2a6f
4 touches
1 conflict
0x02213185…bc8d
0x34b655…2a6f
2 touches
0 conflicts
0x0b5dedb4…e3e8
0x34b655…2a6f
2 touches
0 conflicts
0x1761c637…ed10
0x34b655…2a6f
2 touches
0 conflicts
0x18978822…2623
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
1 conflict on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity