← previous blocknext block →recent activity
Analyzing
Block #89,864,557
15 transactions · 14 stateful · 2026-07-24 08:04:35 UTC
Parallelism
60/100
Blocked
43%
Avg conflicts / tx
1.33
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,864,557 · 15 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w311w012w113w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0x326a02b5…8dad
0x34b655…2a6f
12 touches
15 conflicts
0x6ad97148…cf0d
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x7d02a2c5…9802
0x34b655…2a6f
8 touches
6 conflicts
0x5f447bf3…57c7
0x34b655…2a6f
6 touches
3 conflicts
0x5f394770…ac95
0x34b655…2a6f
4 touches
1 conflict
0x60ca8c7c…9e81
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
15 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity