← previous blocknext block →recent activity
Analyzing
Block #90,574,386
11 transactions · 9 stateful · 2026-07-26 19:55:45 UTC
Parallelism
82/100
Blocked
11%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,574,386 · 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
5w06w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x947f0b4a…a013
0x34b655…2a6f
4 touches
1 conflict
0x947f0b4a…a014
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x21303d7d…b483
0x34b655…2a6f
4 touches
1 conflict
0x316644ac…3590
0x34b655…2a6f
4 touches
1 conflict
0x4d1b8513…6775
0x34b655…2a6f
4 touches
1 conflict
0x4560e5a8…b741
0x34b655…2a6f
2 touches
0 conflicts
0x6fe7d366…78ff
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 0x947f0b4a0f…c4a013
Audit this contract →
← previous block·next block →recent activity