← previous blocknext block →recent activity
Analyzing
Block #89,787,061
21 transactions · 19 stateful · 2026-07-24 01:33:48 UTC
Parallelism
67/100
Blocked
37%
Avg conflicts / tx
1.05
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #89,787,061 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w09w112w013w114w215w316w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4bc1abab…5874
0x34b655…2a6f
14 touches
21 conflicts
0xf3d10975…0d07
0x34b655…2a6f
14 touches
21 conflicts
0xea02471d…1542
0x34b655…2a6f
14 touches
21 conflicts
0xbde524f4…43bf
0x34b655…2a6f
14 touches
21 conflicts
0x042a18e9…bcc6
0x34b655…2a6f
9 touches
10 conflicts
0x7fbb9492…1bf4
0x34b655…2a6f
7 touches
6 conflicts
0x3439dfbc…0d03
0x34b655…2a6f
6 touches
3 conflicts
0x1803586e…d149
0xa6afd3…d132
4 touches
1 conflict
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
21 conflicts on slot 0x4bc1abab4b…a45874
Audit this contract →
← previous block·next block →recent activity