← previous blocknext block →recent activity
Analyzing
Block #89,849,527
36 transactions · 34 stateful · 2026-07-24 06:48:59 UTC
Parallelism
64/100
Blocked
68%
Avg conflicts / tx
3.25
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #89,849,527 · 36 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w08w112w013w114w015w016w117w118w219w220w321w322w423w424w525w526w627w728w629w830w731w832w933w1034w1135w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92339d95…0800
0x0000a8…8888
26 touches
78 conflicts
0x92339d95…0800
0xb1c8ea…8888
18 touches
36 conflicts
0x5ea9eca9…22a6
0x34b655…2a6f
4 touches
1 conflict
0x5ea9eca9…22a7
0x34b655…2a6f
4 touches
1 conflict
0xb54c8ced…5b8c
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe759cbfc…47c8
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: 0x0000a8fd…758888
78 conflicts on slot 0x92339d95cd…a80800
Audit this contract →
← previous block·next block →recent activity