← previous blocknext block →recent activity
Analyzing
Block #89,856,571
19 transactions · 18 stateful · 2026-07-24 07:24:25 UTC
Parallelism
68/100
Blocked
44%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,856,571 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w18w29w311w112w417w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa86351b8…2c5a
0x34b655…2a6f
12 touches
15 conflicts
0xb5a3b1be…8122
0x34b655…2a6f
8 touches
6 conflicts
0x42e8035e…485a
0x34b655…2a6f
6 touches
3 conflicts
0x2c2a227f…b973
0x34b655…2a6f
6 touches
3 conflicts
0x20fbcaee…bb79
0x34b655…2a6f
4 touches
1 conflict
0x2697123c…8526
0x34b655…2a6f
4 touches
1 conflict
0x32bf31bd…1c75
0x34b655…2a6f
4 touches
1 conflict
0x4a5956ef…e226
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: Perpl
15 conflicts on slot 0xa86351b861…d52c5a
Audit this contract →
← previous block·next block →recent activity