← previous blocknext block →recent activity
Analyzing
Block #85,972,455
44 transactions · 25 stateful · 2026-07-06 12:00:26 UTC
Parallelism
86/100
Blocked
44%
Avg conflicts / tx
0.48
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,972,455 · 44 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
6w09w110w214w016w117w218w019w125w330w336w037w438w139w543w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
10 touches
10 conflicts
0x342fbbca…d443
0x40c49f…2af0
8 touches
6 conflicts
0x0d622e34…0000
0x681e90…ae09
8 touches
6 conflicts
0xffa7d0a4…b10a
0x40c49f…2af0
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x8eff8b27…f9ab
0x40c49f…2af0
5 touches
3 conflicts
0x1b60b708…5b4b
0x69df8a…6292
4 touches
1 conflict
0x213ee207…a151
0x69df8a…6292
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