← previous blocknext block →recent activity
Analyzing
Block #90,687,366
10 transactions · 10 stateful · 2026-07-27 05:24:09 UTC
Parallelism
70/100
Blocked
30%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,687,366 · 10 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
2w03w14w25w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x667cf05f…a2d5
0x34b655…2a6f
4 touches
1 conflict
0x4e37574f…4145
0x34b655…2a6f
4 touches
1 conflict
0x0ad4dfbc…941c
0x34b655…2a6f
4 touches
1 conflict
0xb906215a…8acf
0x34b655…2a6f
4 touches
1 conflict
0x08330b36…ae29
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x2b856d86…7988
0x34b655…2a6f
2 touches
0 conflicts
0x52f7c71c…d0a6
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 0x667cf05f38…6aa2d5
Audit this contract →
← previous block·next block →recent activity