← previous blocknext block →recent activity
Analyzing
Block #90,240,611
9 transactions · 9 stateful · 2026-07-25 15:41:53 UTC
Parallelism
56/100
Blocked
44%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,240,611 · 9 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
1w02w13w24w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x96dd83e6…a507
0x34b655…2a6f
4 touches
1 conflict
0x9c87f480…4fbf
0x34b655…2a6f
4 touches
1 conflict
0x9accd401…78db
0x34b655…2a6f
4 touches
1 conflict
0xb7575337…7b9a
0x34b655…2a6f
4 touches
1 conflict
0xb7575337…7b9b
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x2a4568fd…f2de
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
1 conflict on slot 0x96dd83e650…3fa507
Audit this contract →
← previous block·next block →recent activity