← previous blocknext block →recent activity
Analyzing
Block #90,824,216
16 transactions · 16 stateful · 2026-07-27 16:52:42 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,824,216 · 16 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
1w02w03w04w05w16w18w19w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69a45f39…39aa
0x34b655…2a6f
6 touches
3 conflicts
0x80656e3b…9240
0x34b655…2a6f
6 touches
3 conflicts
0x22755bc3…3056
0x34b655…2a6f
4 touches
1 conflict
0x31b06932…8a2e
0x34b655…2a6f
4 touches
1 conflict
0x3c0e49c9…7833
0x34b655…2a6f
4 touches
1 conflict
0x5146ef12…80c6
0x34b655…2a6f
4 touches
1 conflict
0x6ca5d200…2cbf
0x34b655…2a6f
4 touches
1 conflict
0x6ec11f62…98a6
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 0x69a45f39d6…c739aa
Audit this contract →
← previous block·next block →recent activity