← previous blocknext block →recent activity
Analyzing
Block #86,623,619
43 transactions · 33 stateful · 2026-07-09 12:31:29 UTC
Parallelism
79/100
Blocked
67%
Avg conflicts / tx
1.23
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #86,623,619 · 43 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w010w211w313w414w517w118w019w120w223w324w432w433w534w640w741w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0x8a35acfb…d1a8
0xb1dbf0…c0d3
10 touches
10 conflicts
0x8a35acfb…d1a7
0xb1dbf0…c0d3
10 touches
10 conflicts
0xffa7d0a4…b10a
0x40c49f…2af0
8 touches
6 conflicts
0x57de6cd8…e44a
0x34b655…2a6f
6 touches
3 conflicts
0x60c7217a…8c94
0x34b655…2a6f
6 touches
3 conflicts
0x842fd3e2…81d1
0x34b655…2a6f
6 touches
3 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: 0x40c49f17…d22af0
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity