← previous blocknext block →recent activity
Analyzing
Block #90,531,163
10 transactions · 10 stateful · 2026-07-26 16:18:21 UTC
Parallelism
50/100
Blocked
40%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,531,163 · 10 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w36w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb64499f6…c37a
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x0eac7709…66c3
0x34b655…2a6f
4 touches
1 conflict
0x29a2aad6…286b
0x34b655…2a6f
4 touches
1 conflict
0x2c7f2108…99fc
0x34b655…2a6f
4 touches
1 conflict
0x2c7f2108…99fd
0x34b655…2a6f
4 touches
1 conflict
0x53f393fa…00b9
0x34b655…2a6f
4 touches
1 conflict
0x59572298…7f94
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
6 conflicts on slot 0xb64499f66a…c3c37a
Audit this contract →
← previous block·next block →recent activity