← previous blocknext block →recent activity
Analyzing
Block #89,581,351
16 transactions · 14 stateful · 2026-07-23 06:11:32 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,581,351 · 16 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
1w02w19w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdaf5ed0d…16ae
0x34b655…2a6f
4 touches
1 conflict
0xdaf5ed0d…16af
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x1cda18d5…31c3
0x34b655…2a6f
4 touches
1 conflict
0xa7013be2…c0a8
0x34b655…2a6f
4 touches
1 conflict
0xa85efb73…a0c1
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 0xdaf5ed0d35…7116ae
Audit this contract →
← previous block·next block →recent activity