← previous blocknext block →recent activity
Analyzing
Block #89,710,423
30 transactions · 29 stateful · 2026-07-23 19:06:47 UTC
Parallelism
63/100
Blocked
76%
Avg conflicts / tx
3.5
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #89,710,423 · 30 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w29w010w011w112w113w214w215w316w317w418w419w520w621w522w723w824w625w926w727w828w929w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92339d95…0800
0x0000a8…8888
22 touches
55 conflicts
0x92339d95…0800
0xb1c8ea…8888
20 touches
45 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x8218911e…3bed
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x9b2d3bee…8eec
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eeb
0x34b655…2a6f
4 touches
1 conflict
0xef048f92…572b
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
55 conflicts on slot 0x92339d95cd…a80800
Audit this contract →
← previous block·next block →recent activity