← previous blocknext block →recent activity
Analyzing
Block #89,745,217
43 transactions · 40 stateful · 2026-07-23 22:02:33 UTC
Parallelism
56/100
Blocked
80%
Avg conflicts / tx
6.12
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #89,745,217 · 43 txs across 19 waves · depth 19
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
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w08w19w010w113w214w316w417w519w620w722w823w925w1026w1128w1230w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92339d95…0800
0x0000a8…8888
38 touches
171 conflicts
0x92339d95…0800
0xb1c8ea…8888
28 touches
91 conflicts
0x917f99a5…7989
0x34b655…2a6f
4 touches
1 conflict
0x3a921be0…779c
0x2a68ba…90c5
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x213ee207…a151
0x2b46c0…1669
2 touches
0 conflicts
0x46279ae7…20dd
0x2b46c0…1669
2 touches
0 conflicts
0x53e50026…6d8c
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
171 conflicts on slot 0x92339d95cd…a80800
Audit this contract →
← previous block·next block →recent activity