← previous blocknext block →recent activity
Analyzing
Block #90,206,514
8 transactions · 7 stateful · 2026-07-25 12:50:00 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,206,514 · 8 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
3w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26607bc2…7fd6
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x12028e5c…112a
0x34b655…2a6f
2 touches
0 conflicts
0x1d0aee67…c737
0x34b655…2a6f
2 touches
0 conflicts
0x4560e5a8…b741
0x34b655…2a6f
2 touches
0 conflicts
0x502b3ee1…7f7b
0x34b655…2a6f
2 touches
0 conflicts
0x502b3ee1…7f7c
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 0x26607bc28d…b87fd6
Audit this contract →
← previous block·next block →recent activity