← previous blocknext block →recent activity
Analyzing
Block #89,735,303
5 transactions · 5 stateful · 2026-07-23 21:12:25 UTC
Parallelism
60/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,735,303 · 5 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
0x0a57a2b8…3cdd
0x34b655…2a6f
4 touches
1 conflict
0x03fb27fd…0c06
0x34b655…2a6f
2 touches
0 conflicts
0x100593c2…32ce
0x34b655…2a6f
2 touches
0 conflicts
0x17f9163a…1201
0x34b655…2a6f
2 touches
0 conflicts
0x23d25769…fc56
0x34b655…2a6f
2 touches
0 conflicts
0x3de86e79…4d3d
0x34b655…2a6f
2 touches
0 conflicts
0x48028c31…6829
0x34b655…2a6f
2 touches
0 conflicts
0x5dd18eb2…4d66
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 0x0a57a2b8cd…773cdd
Audit this contract →
← previous block·next block →recent activity