← previous blocknext block →recent activity
Analyzing
Block #90,689,086
6 transactions · 6 stateful · 2026-07-27 05:32:48 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,689,086 · 6 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64c6190b…498c
0x34b655…2a6f
4 touches
1 conflict
0x9775559a…a8ec
0x34b655…2a6f
4 touches
1 conflict
0xcef70a96…db44
0x34b655…2a6f
4 touches
1 conflict
0x5231576b…27a1
0x34b655…2a6f
3 touches
1 conflict
0x285e320d…f3a0
0x34b655…2a6f
2 touches
0 conflicts
0x42b04648…21d2
0x34b655…2a6f
2 touches
0 conflicts
0x4360b49f…140d
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
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 0x64c6190bee…97498c
Audit this contract →
← previous block·next block →recent activity