← previous blocknext block →recent activity
Analyzing
Block #89,735,548
50 transactions · 48 stateful · 2026-07-23 21:13:39 UTC
Parallelism
54/100
Blocked
77%
Avg conflicts / tx
6.74
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #89,735,548 · 50 txs across 23 waves · depth 23
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
wave w21
wave w22
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w28w312w013w116w217w320w421w524w625w728w831w933w1035w1137w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92339d95…0800
0x0000a8…8888
46 touches
253 conflicts
0x92339d95…0800
0xb1c8ea…8888
26 touches
78 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xa3f095f5…bd87
0x34b655…2a6f
6 touches
3 conflicts
0xc6b604e6…5152
0x34b655…2a6f
4 touches
1 conflict
0x8f63f383…6eda
0x34b655…2a6f
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
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: 0x0000a8fd…758888
253 conflicts on slot 0x92339d95cd…a80800
Audit this contract →
← previous block·next block →recent activity