← previous blocknext block →recent activity
Analyzing
Block #85,344,278
35 transactions · 24 stateful · 2026-07-03 14:15:30 UTC
Parallelism
91/100
Blocked
46%
Avg conflicts / tx
0.37
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,344,278 · 35 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
1w07w010w011w116w017w119w122w023w125w126w227w128w229w130w133w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xcdc1731c…b91a
0x34b655…2a6f
6 touches
3 conflicts
0x666c036f…a538
0xd32edf…ff58
5 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xabf8e9e0…2ed8
0x40c49f…2af0
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
3 conflicts on slot 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity