← previous blocknext block →recent activity
Analyzing
Block #89,698,436
13 transactions · 13 stateful · 2026-07-23 18:06:23 UTC
Parallelism
69/100
Blocked
23%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,698,436 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5ea108a…dbf6
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd83879b2…0bfb
0x34b655…2a6f
4 touches
1 conflict
0xe25eabc5…56e6
0x34b655…2a6f
4 touches
1 conflict
0x03cf8a66…08c6
0x34b655…2a6f
4 touches
1 conflict
0x6479b9ca…d2eb
0x34b655…2a6f
4 touches
1 conflict
0x701208a7…46b3
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 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 0xf5ea108a6a…e5dbf6
Audit this contract →
← previous block·next block →recent activity