← previous blocknext block →recent activity
Analyzing
Block #89,827,350
19 transactions · 17 stateful · 2026-07-24 04:57:06 UTC
Parallelism
68/100
Blocked
59%
Avg conflicts / tx
1.16
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,827,350 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w27w19w010w011w112w113w214w315w216w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92339d95…0800
0xb1c8ea…8888
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x92339d95…0800
0x0000a8…8888
6 touches
3 conflicts
0x824f72df…df4a
0x34b655…2a6f
4 touches
1 conflict
0x4cabb80a…46bf
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x5a100ac0…96d3
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: 0xb1c8ead4…c38888
15 conflicts on slot 0x92339d95cd…a80800
Audit this contract →
← previous block·next block →recent activity