← previous blocknext block →recent activity
Analyzing
Block #89,862,742
27 transactions · 26 stateful · 2026-07-24 07:55:27 UTC
Parallelism
37/100
Blocked
77%
Avg conflicts / tx
5.41
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #89,862,742 · 27 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w07w18w19w210w211w312w413w314w415w516w617w718w819w920w1021w1122w1223w1324w1425w1526w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92339d95…0800
0x0000a8…8888
34 touches
136 conflicts
0x92339d95…0800
0xb1c8ea…8888
10 touches
10 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
2 touches
0 conflicts
0x40970e69…da50
0x2b46c0…1669
2 touches
0 conflicts
0x8cf3d245…1d0d
0x2b46c0…1669
2 touches
0 conflicts
0xb05cd4f5…73d0
0x2b46c0…1669
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
136 conflicts on slot 0x92339d95cd…a80800
Audit this contract →
← previous block·next block →recent activity