← previous blocknext block →recent activity
Analyzing
Block #89,681,271
7 transactions · 6 stateful · 2026-07-23 16:39:48 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,681,271 · 7 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
1w02w15w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c82e363…09ce
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x8e5cc690…b06b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x00f6a8a7…0e6e
0x34b655…2a6f
2 touches
0 conflicts
0x085e35d2…8d1f
0x34b655…2a6f
2 touches
0 conflicts
0x085e35d2…8d20
0x34b655…2a6f
2 touches
0 conflicts
0x363a4317…87d2
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 0x0c82e363df…ee09ce
Audit this contract →
← previous block·next block →recent activity