← previous blocknext block →recent activity
Analyzing
Block #90,514,892
12 transactions · 11 stateful · 2026-07-26 14:56:30 UTC
Parallelism
83/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,514,892 · 12 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
5w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe20c6bc5…753c
0x34b655…2a6f
4 touches
1 conflict
0xb36a727b…862c
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0xb36a727b…862b
0x34b655…2a6f
4 touches
1 conflict
0x365bd58a…0eb5
0x34b655…2a6f
2 touches
0 conflicts
0x8b46e9d1…e148
0x34b655…2a6f
2 touches
0 conflicts
0x8e5cc690…b06b
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 0xe20c6bc582…fb753c
Audit this contract →
← previous block·next block →recent activity