← previous blocknext block →recent activity
Analyzing
Block #86,713,469
28 transactions · 22 stateful · 2026-07-09 22:32:38 UTC
Parallelism
86/100
Blocked
45%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,713,469 · 28 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w09w010w111w012w113w214w116w122w223w024w125w226w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0dbf9688…c6cf
0x43cf54…7777
6 touches
3 conflicts
0x0159e8ca…1dc4
0xd32edf…ff58
5 touches
3 conflicts
0x3d49013e…1338
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7017d770…abbd
0x34b655…2a6f
4 touches
1 conflict
0x7017d770…abbe
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4ab
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: 0x43cf5407…d87777
3 conflicts on slot 0x0dbf9688de…b0c6cf
Audit this contract →
← previous block·next block →recent activity