← previous blocknext block →recent activity
Analyzing
Block #89,858,656
16 transactions · 15 stateful · 2026-07-24 07:34:54 UTC
Parallelism
56/100
Blocked
60%
Avg conflicts / tx
1.31
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #89,858,656 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w27w38w29w410w511w614w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x374bd962…f660
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x459cbb60…8957
0x34b655…2a6f
8 touches
6 conflicts
0xda27c764…7fab
0x34b655…2a6f
6 touches
3 conflicts
0xf7676b34…7209
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x87a31acd…1f04
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
6 conflicts on slot 0x374bd962ca…a5f660
Audit this contract →
← previous block·next block →recent activity