← previous blocknext block →recent activity
Analyzing
Block #90,822,716
20 transactions · 18 stateful · 2026-07-27 16:45:10 UTC
Parallelism
80/100
Blocked
39%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,822,716 · 20 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
3w05w16w07w111w212w115w216w317w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xbb384cb4…9cde
0x34b655…2a6f
6 touches
3 conflicts
0x9aec6b2a…5725
0x34b655…2a6f
6 touches
3 conflicts
0x23ce455e…41ae
0x34b655…2a6f
4 touches
1 conflict
0x4f3a6b4a…3819
0x34b655…2a6f
4 touches
1 conflict
0x6771eae2…7014
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x7d6b9af1…9a38
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
3 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity