← previous blocknext block →recent activity
Analyzing
Block #89,518,523
18 transactions · 16 stateful · 2026-07-22 23:11:56 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,518,523 · 18 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
3w04w15w26w38w011w112w013w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x10a2bd5d…ad6d
0x8d1565…6723
8 touches
6 conflicts
0x6ee30d14…7c60
0x336ed4…c59c
8 touches
6 conflicts
0x00000000…000b
0x90c374…be45
8 touches
6 conflicts
0x00000000…000a
0x90c374…be45
8 touches
6 conflicts
0x01119579…40ad
0x336ed4…c59c
6 touches
3 conflicts
0xc9c85b7b…d25c
0x8d1565…6723
6 touches
3 conflicts
0xcbdf6f54…d089
0x8d1565…6723
6 touches
3 conflicts
0xb26fce3e…f47f
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: 0x8d156514…236723
6 conflicts on slot 0x10a2bd5d43…51ad6d
Audit this contract →
← previous block·next block →recent activity