← previous blocknext block →recent activity
Analyzing
Block #90,499,689
7 transactions · 7 stateful · 2026-07-26 13:40:02 UTC
Parallelism
71/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,499,689 · 7 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd0fdbef…b0d0
0x34b655…2a6f
4 touches
1 conflict
0x5fdeee5f…f6c3
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x808129fc…f97d
0x34b655…2a6f
4 touches
1 conflict
0x1c3295fd…097a
0x34b655…2a6f
2 touches
0 conflicts
0x25d4df98…4fa4
0x34b655…2a6f
2 touches
0 conflicts
0x3d3e4985…bee4
0x34b655…2a6f
2 touches
0 conflicts
0x5626acdd…8f9d
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 0xcd0fdbef85…83b0d0
Audit this contract →
← previous block·next block →recent activity