← previous blocknext block →recent activity
Analyzing
Block #90,879,309
17 transactions · 17 stateful · 2026-07-27 21:29:53 UTC
Parallelism
76/100
Blocked
35%
Avg conflicts / tx
0.76
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,879,309 · 17 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
4w05w18w010w111w212w215w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x06726618…fafd
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc3fc40da…1c60
0x34b655…2a6f
6 touches
3 conflicts
0xd2e482cc…0a50
0x34b655…2a6f
6 touches
3 conflicts
0x3deaf71f…c229
0x34b655…2a6f
4 touches
1 conflict
0x41e2ea73…ddf8
0x34b655…2a6f
4 touches
1 conflict
0x427dec7f…61c6
0x34b655…2a6f
4 touches
1 conflict
0x4b912362…084d
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
6 conflicts on slot 0x06726618f7…29fafd
Audit this contract →
← previous block·next block →recent activity