← previous blocknext block →recent activity
Analyzing
Block #89,536,349
16 transactions · 14 stateful · 2026-07-23 01:10:55 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,536,349 · 16 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
2w08w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb733b9da…9c31
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x06df379f…2653
0x34b655…2a6f
2 touches
0 conflicts
0x13981d20…e8b5
0x34b655…2a6f
2 touches
0 conflicts
0x2bac71c3…3296
0x34b655…2a6f
2 touches
0 conflicts
0x424b9133…252a
0x34b655…2a6f
2 touches
0 conflicts
0x427f51fd…bd80
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 0xb733b9dad9…879c31
Audit this contract →
← previous block·next block →recent activity