← previous blocknext block →recent activity
Analyzing
Block #89,378,480
30 transactions · 18 stateful · 2026-07-22 07:36:06 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,378,480 · 30 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
1w04w05w16w27w316w117w428w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xd600045a…99b4
0x40c49f…2af0
4 touches
1 conflict
0xd8b6194e…cdf0
0x40c49f…2af0
4 touches
1 conflict
0x1e4b5386…df72
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x52e69143…95ad
0x065c9d…c394
4 touches
1 conflict
0xce827910…ff22
0x065c9d…c394
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
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: Kuru Exchange: MarginAccount
6 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity