← previous blocknext block →recent activity
Analyzing
Block #85,132,541
30 transactions · 25 stateful · 2026-07-02 14:45:09 UTC
Parallelism
87/100
Blocked
40%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,132,541 · 30 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
1w02w18w011w112w213w315w117w019w122w224w227w228w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x06040b44…e244
0x34b655…2a6f
8 touches
6 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
8 touches
6 conflicts
0x6ca32a09…4e48
0x34b655…2a6f
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0x7af4b011…96f5
0x34b655…2a6f
6 touches
3 conflicts
0x93cf2dc3…5f02
0x34b655…2a6f
6 touches
3 conflicts
0x97c67486…27fe
0x34b655…2a6f
6 touches
3 conflicts
0xbbb9fa77…d121
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x06040b44e2…0de244
Audit this contract →
← previous block·next block →recent activity