← previous blocknext block →recent activity
Analyzing
Block #89,785,291
10 transactions · 9 stateful · 2026-07-24 01:24:52 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,785,291 · 10 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
3w04w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x39a45f01…2b79
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x3439dfbc…0d03
0x34b655…2a6f
4 touches
1 conflict
0x55623421…30d4
0x065c9d…c394
2 touches
0 conflicts
0x56752dcb…9ff8
0x065c9d…c394
2 touches
0 conflicts
0x94889b01…3db5
0x065c9d…c394
2 touches
0 conflicts
0x9a0879ab…b0b4
0x065c9d…c394
2 touches
0 conflicts
0xb33ff823…1188
0x065c9d…c394
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 0x39a45f0156…d32b79
Audit this contract →
← previous block·next block →recent activity