← previous blocknext block →recent activity
Analyzing
Block #89,700,605
23 transactions · 20 stateful · 2026-07-23 18:17:18 UTC
Parallelism
70/100
Blocked
55%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #89,700,605 · 23 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
3w05w06w17w28w310w211w314w116w217w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd0f6f4f2…dffa
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xf5ea108a…dbf6
0x34b655…2a6f
8 touches
6 conflicts
0x08330b36…ae29
0x34b655…2a6f
6 touches
3 conflicts
0x424934c8…f2f1
0x34b655…2a6f
6 touches
3 conflicts
0x9ff6dd4d…e44d
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x9577c5b8…b791
0x34b655…2a6f
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
6 conflicts on slot 0xd0f6f4f225…4cdffa
Audit this contract →
← previous block·next block →recent activity