← previous blocknext block →recent activity
Analyzing
Block #90,541,511
11 transactions · 11 stateful · 2026-07-26 17:10:24 UTC
Parallelism
82/100
Blocked
9%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,541,511 · 11 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
2w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdc6c3cd8…643a
0x34b655…2a6f
4 touches
1 conflict
0xeb4a89da…a6db
0x34b655…2a6f
4 touches
1 conflict
0xfaa5c672…5681
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x859fe39d…effa
0x34b655…2a6f
4 touches
1 conflict
0xbedefe84…fc7b
0x34b655…2a6f
4 touches
1 conflict
0x70a53d84…2d91
0x754704…b603
2 touches
0 conflicts
0xa949d556…184c
0x754704…b603
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 0xdc6c3cd83f…05643a
Audit this contract →
← previous block·next block →recent activity