← previous blocknext block →recent activity
Analyzing
Block #89,677,457
10 transactions · 9 stateful · 2026-07-23 16:20:34 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,677,457 · 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
1w02w03w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x536f894b…2597
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x6b0d2ce5…ff19
0x34b655…2a6f
4 touches
1 conflict
0xdc8d4ee0…def3
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4327afd2…1b3a
0x34b655…2a6f
2 touches
0 conflicts
0x63c900f4…2600
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 0x536f894bd4…e82597
Audit this contract →
← previous block·next block →recent activity