← previous blocknext block →recent activity
Analyzing
Block #89,582,326
23 transactions · 21 stateful · 2026-07-23 06:18:03 UTC
Parallelism
74/100
Blocked
38%
Avg conflicts / tx
0.87
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,582,326 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w07w18w213w117w018w119w220w321w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x7a2fc410…c088
0x34b655…2a6f
6 touches
3 conflicts
0x548145a9…cfce
0x34b655…2a6f
4 touches
1 conflict
0x5554e43d…2811
0x34b655…2a6f
4 touches
1 conflict
0x5970f182…41e2
0x34b655…2a6f
4 touches
1 conflict
0x59f08f52…6487
0x34b655…2a6f
4 touches
1 conflict
0x65dcf957…eefd
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity