← previous blocknext block →recent activity
Analyzing
Block #90,894,853
12 transactions · 11 stateful · 2026-07-27 22:48:04 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,894,853 · 12 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
3w04w16w07w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe73b93bf…c0e1
0x34b655…2a6f
6 touches
3 conflicts
0x021db3e8…a280
0x34b655…2a6f
4 touches
1 conflict
0x10af5537…5a9a
0x34b655…2a6f
4 touches
1 conflict
0x16f8e14a…f6e4
0x34b655…2a6f
4 touches
1 conflict
0x1c796c6b…064e
0x34b655…2a6f
4 touches
1 conflict
0x322fa8a2…7d2d
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4e8c6c21…a65a
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 0xe73b93bf37…0bc0e1
Audit this contract →
← previous block·next block →recent activity