← previous blocknext block →recent activity
Analyzing
Block #89,547,592
21 transactions · 19 stateful · 2026-07-23 02:26:05 UTC
Parallelism
76/100
Blocked
42%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,547,592 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w28w311w413w314w418w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67bfbc55…7b2f
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6426
0x34b655…2a6f
6 touches
3 conflicts
0x30e3f228…0d43
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x5d7f309d…5145
0x34b655…2a6f
4 touches
1 conflict
0x5f6ac0ab…d565
0x34b655…2a6f
4 touches
1 conflict
0x64aaadbf…f9f3
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
3 conflicts on slot 0x67bfbc5533…247b2f
Audit this contract →
← previous block·next block →recent activity