← previous blocknext block →recent activity
Analyzing
Block #90,535,401
10 transactions · 8 stateful · 2026-07-26 16:39:39 UTC
Parallelism
60/100
Blocked
38%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,535,401 · 10 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
4w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0xfb70218e…3367
0x34b655…2a6f
6 touches
3 conflicts
0x62b26c37…87d6
0x34b655…2a6f
6 touches
3 conflicts
0xf61165ef…adb9
0x34b655…2a6f
6 touches
3 conflicts
0x9c1ef3e4…fb46
0x34b655…2a6f
5 touches
3 conflicts
0x28f4f6bc…be52
0x34b655…2a6f
4 touches
1 conflict
0x3bdd71a2…b6eb
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 0x0000000000…0000c9
Audit this contract →
← previous block·next block →recent activity