← previous blocknext block →recent activity
Analyzing
Block #89,871,448
24 transactions · 21 stateful · 2026-07-24 08:39:15 UTC
Parallelism
75/100
Blocked
43%
Avg conflicts / tx
0.96
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,871,448 · 24 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
2w03w14w25w39w010w011w112w113w216w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b5101ac…090b
0x34b655…2a6f
12 touches
15 conflicts
0xdf39e0b5…6504
0x34b655…2a6f
8 touches
6 conflicts
0xa6f06b03…5c15
0xd32edf…ff58
7 touches
6 conflicts
0x59dccbd8…2bf6
0x34b655…2a6f
6 touches
3 conflicts
0x6c87ba93…686c
0x34b655…2a6f
6 touches
3 conflicts
0x8b86b2c7…5a5a
0x34b655…2a6f
6 touches
3 conflicts
0x97790153…3866
0x34b655…2a6f
6 touches
3 conflicts
0xa98e6cb0…8051
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0x2b5101acd1…7c090b
Audit this contract →
← previous block·next block →recent activity