← previous blocknext block →recent activity
Analyzing
Block #85,901,244
16 transactions · 13 stateful · 2026-07-06 04:05:42 UTC
Parallelism
88/100
Blocked
8%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,901,244 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a134c1f…857a
0x34b655…2a6f
4 touches
1 conflict
0xd14e54cf…c8c7
0x34b655…2a6f
4 touches
1 conflict
0x1a607703…ec50
0x34b655…2a6f
4 touches
1 conflict
0x1fd84d4b…1a6e
0x34b655…2a6f
4 touches
1 conflict
0x157dbfb2…4089
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad07
0x34b655…2a6f
4 touches
1 conflict
0x16e9dcb1…a993
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcc
0x34b655…2a6f
2 touches
0 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: Perpl
1 conflict on slot 0x8a134c1fdb…bc857a
Audit this contract →
← previous block·next block →recent activity