← previous blocknext block →recent activity
Analyzing
Block #89,736,587
7 transactions · 6 stateful · 2026-07-23 21:18:55 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,736,587 · 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67bfbc55…7b2f
0x34b655…2a6f
4 touches
1 conflict
0xaf151f7f…3fe4
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x03fb27fd…0c06
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x53142478…5458
0x34b655…2a6f
2 touches
0 conflicts
0x58d6b9cf…7c9e
0x34b655…2a6f
2 touches
0 conflicts
0x5d13f460…b15b
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 0x67bfbc5533…247b2f
Audit this contract →
← previous block·next block →recent activity