← previous blocknext block →recent activity
Analyzing
Block #89,673,937
24 transactions · 21 stateful · 2026-07-23 16:02:36 UTC
Parallelism
71/100
Blocked
48%
Avg conflicts / tx
0.88
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #89,673,937 · 24 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
2w06w07w18w09w110w211w314w115w217w320w421w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x574a8378…b246
0x34b655…2a6f
8 touches
6 conflicts
0x6aea3f64…bb1f
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xe068f0d8…ac71
0x34b655…2a6f
6 touches
3 conflicts
0xebeee24a…ed8d
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xf9ac650a…d82d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x574a83789c…23b246
Audit this contract →
← previous block·next block →recent activity