← previous blocknext block →recent activity
Analyzing
Block #90,866,182
5 transactions · 5 stateful · 2026-07-27 20:23:51 UTC
Parallelism
40/100
Blocked
40%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,866,182 · 5 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
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x74f95963…01a2
0x34b655…2a6f
4 touches
1 conflict
0x81561f70…fefd
0x34b655…2a6f
4 touches
1 conflict
0xda95d80c…a64c
0x34b655…2a6f
4 touches
1 conflict
0x1e137b39…bae2
0x34b655…2a6f
2 touches
0 conflicts
0x2121b1b0…cc4e
0x34b655…2a6f
2 touches
0 conflicts
0x59e99bd9…4df6
0x34b655…2a6f
2 touches
0 conflicts
0x64275949…d698
0x34b655…2a6f
2 touches
0 conflicts
0x6536722f…6b4e
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 0x74f9596374…0201a2
Audit this contract →
← previous block·next block →recent activity