← previous blocknext block →recent activity
Analyzing
Block #85,170,306
14 transactions · 9 stateful · 2026-07-02 18:56:44 UTC
Parallelism
79/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,170,306 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w08w19w213w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc1aad6e5…9135
0x34b655…2a6f
4 touches
2 conflicts
0x70638c24…1553
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x043488e6…2455
0x34b655…2a6f
2 touches
0 conflicts
0x0b943daa…2c60
0x34b655…2a6f
2 touches
0 conflicts
0x100510c3…63be
0x34b655…2a6f
2 touches
0 conflicts
0x181732de…9796
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
2 conflicts on slot 0xc1aad6e5d4…f89135
Audit this contract →
← previous block·next block →recent activity