← previous blocknext block →recent activity
Analyzing
Block #90,535,336
11 transactions · 11 stateful · 2026-07-26 16:39:20 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,535,336 · 11 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
1w05w16w29w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e56f6b6…5940
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x6c60fbcf…8744
0x34b655…2a6f
6 touches
3 conflicts
0x1c097b81…0164
0x34b655…2a6f
4 touches
1 conflict
0x296b498d…22e2
0x34b655…2a6f
4 touches
1 conflict
0x38a5a994…d210
0x34b655…2a6f
4 touches
1 conflict
0xe7c1aa35…e064
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
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 0x1e56f6b6e1…615940
Audit this contract →
← previous block·next block →recent activity