← previous blocknext block →recent activity
Analyzing
Block #89,856,881
38 transactions · 37 stateful · 2026-07-24 07:25:58 UTC
Parallelism
60/100
Blocked
65%
Avg conflicts / tx
3.58
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #89,856,881 · 38 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
4w05w19w114w215w016w017w118w119w220w221w322w323w424w425w526w527w628w629w730w731w832w933w1034w1135w1236w1337w14
- 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
16 touches
28 conflicts
0x734ee320…caae
0x34b655…2a6f
4 touches
1 conflict
0x0a57a2b8…3cdd
0x34b655…2a6f
4 touches
1 conflict
0x4c2e9ab4…375e
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x181ad9cf…26f4
0x34b655…2a6f
2 touches
0 conflicts
0x258fcaf5…2084
0x34b655…2a6f
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
105 conflicts on slot 0x92339d95cd…a80800
Audit this contract →
← previous block·next block →recent activity