← previous blocknext block →recent activity
Analyzing
Block #90,857,061
10 transactions · 10 stateful · 2026-07-27 19:37:55 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,857,061 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4dc6cd61…f674
0x34b655…2a6f
4 touches
1 conflict
0x7032dc14…49ea
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x365bd58a…0eb5
0x34b655…2a6f
4 touches
1 conflict
0x664bf99e…0a8c
0x34b655…2a6f
4 touches
1 conflict
0xc3e19352…2faf
0x34b655…2a6f
4 touches
1 conflict
0x7506443a…4820
0x34b655…2a6f
2 touches
0 conflicts
0xbca4de0c…577c
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 0x4dc6cd6114…b6f674
Audit this contract →
← previous block·next block →recent activity