← previous blocknext block →recent activity
Analyzing
Block #85,987,780
37 transactions · 25 stateful · 2026-07-06 13:42:54 UTC
Parallelism
78/100
Blocked
44%
Avg conflicts / tx
0.7
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,987,780 · 37 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w113w215w316w417w018w520w121w622w727w028w134w235w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
10 touches
10 conflicts
0xd16df6cd…5532
0x40c49f…2af0
8 touches
6 conflicts
0xf5310ef7…485a
0x40c49f…2af0
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x23eb943e…64b9
0x40c49f…2af0
4 touches
2 conflicts
0xa486f342…64d5
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: 0x40c49f17…d22af0
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity