← previous blocknext block →recent activity
Analyzing
Block #89,786,537
39 transactions · 38 stateful · 2026-07-24 01:31:09 UTC
Parallelism
62/100
Blocked
76%
Avg conflicts / tx
4.26
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #89,786,537 · 39 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w28w39w213w014w015w116w117w218w219w320w421w322w523w424w625w526w727w628w829w730w931w832w1033w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92339d95…0800
0x0000a8…8888
30 touches
105 conflicts
0x92339d95…0800
0xb1c8ea…8888
22 touches
55 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x0494220d…abf6
0x34b655…2a6f
4 touches
1 conflict
0x0494220d…abf7
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x24551912…0fa7
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
105 conflicts on slot 0x92339d95cd…a80800
Audit this contract →
← previous block·next block →recent activity