← previous blocknext block →recent activity
Analyzing
Block #89,692,656
22 transactions · 17 stateful · 2026-07-23 17:37:15 UTC
Parallelism
82/100
Blocked
41%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,692,656 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w07w29w313w015w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0xbb97db90…4c93
0xc8689a…ee79
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xa4f80979…4d71
0x065c9d…c394
4 touches
1 conflict
0xd35bb5ac…3586
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
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: 0x681e908b…e1ae09
3 conflicts on slot 0x0d622e34f9…000000
Audit this contract →
← previous block·next block →recent activity