← previous blocknext block →recent activity
Analyzing
Block #89,539,112
10 transactions · 10 stateful · 2026-07-23 01:29:24 UTC
Parallelism
70/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,539,112 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9e70dadd…810e
0x34b655…2a6f
4 touches
1 conflict
0x9e70dadd…810d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcc282b3d…e139
0x34b655…2a6f
4 touches
1 conflict
0xe96d3dde…7a2e
0x34b655…2a6f
4 touches
1 conflict
0x9f518b17…a0a6
0x34b655…2a6f
2 touches
0 conflicts
0xa2c8d052…a91b
0x34b655…2a6f
2 touches
0 conflicts
0xb69ee92a…1ec5
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 0x9e70dadd35…1b810e
Audit this contract →
← previous block·next block →recent activity