← previous blocknext block →recent activity
Analyzing
Block #89,752,458
12 transactions · 10 stateful · 2026-07-23 22:39:08 UTC
Parallelism
83/100
Blocked
40%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,752,458 · 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
2w04w05w17w18w09w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a57a2b8…3cdd
0x34b655…2a6f
4 touches
1 conflict
0x320178e8…b5f6
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xe8b6e4c2…e20a
0x188d58…ea8e
4 touches
1 conflict
0x0dbf9688…c6cf
0x43cf54…7777
4 touches
1 conflict
0x46e20173…2952
0xd32edf…ff58
3 touches
1 conflict
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 0x0a57a2b8cd…773cdd
Audit this contract →
← previous block·next block →recent activity