← previous blocknext block →recent activity
Analyzing
Block #90,454,693
6 transactions · 6 stateful · 2026-07-26 09:53:38 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,454,693 · 6 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70b7b52e…7743
0x34b655…2a6f
4 touches
1 conflict
0x70b7b52e…7744
0x34b655…2a6f
4 touches
1 conflict
0x7118f456…6083
0x34b655…2a6f
4 touches
1 conflict
0x09a168cc…dcc0
0x34b655…2a6f
2 touches
0 conflicts
0x149ea1fb…e34a
0x34b655…2a6f
2 touches
0 conflicts
0x2df6f59b…d662
0x34b655…2a6f
2 touches
0 conflicts
0x3dff16b2…ffff
0x34b655…2a6f
2 touches
0 conflicts
0x3e1b21c6…b1e4
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 0x70b7b52e5b…0a7743
Audit this contract →
← previous block·next block →recent activity