← previous blocknext block →recent activity
Analyzing
Block #89,573,593
14 transactions · 13 stateful · 2026-07-23 05:19:48 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,573,593 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w08w19w110w211w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd6c0349d…05b0
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x21e273cb…b384
0x34b655…2a6f
4 touches
1 conflict
0xfb0579c5…af8d
0x40c49f…2af0
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x8c95a046…d593
0x40c49f…2af0
4 touches
1 conflict
0x46279ae7…20dd
0x2b46c0…1669
2 touches
0 conflicts
0x53e50026…6d8c
0x2b46c0…1669
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 0xd6c0349d4b…1105b0
Audit this contract →
← previous block·next block →recent activity