← previous blocknext block →recent activity
Analyzing
Block #85,914,842
21 transactions · 18 stateful · 2026-07-06 05:36:15 UTC
Parallelism
76/100
Blocked
39%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,914,842 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w09w110w113w114w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbffde283…3385
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x35a9f06c…7689
0x34b655…2a6f
6 touches
3 conflicts
0x5fc1d933…62d0
0x34b655…2a6f
6 touches
3 conflicts
0x2895e9ff…95e9
0x34b655…2a6f
4 touches
1 conflict
0x5632a0f0…14bb
0x34b655…2a6f
4 touches
1 conflict
0x5e782d17…5317
0x34b655…2a6f
4 touches
1 conflict
0x5e782d17…5318
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: Perpl
6 conflicts on slot 0xbffde283d8…c63385
Audit this contract →
← previous block·next block →recent activity