← previous blocknext block →recent activity
Analyzing
Block #85,138,025
35 transactions · 30 stateful · 2026-07-02 15:21:45 UTC
Parallelism
89/100
Blocked
33%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,138,025 · 35 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
2w03w05w17w08w210w011w116w021w022w123w024w127w128w229w331w232w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3c7520fc…9ca3
0x34b655…2a6f
8 touches
6 conflicts
0x133f6ee2…1e71
0xd32edf…ff58
7 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xba6ffa8a…77d5
0x34b655…2a6f
6 touches
3 conflicts
0xe1791476…927a
0x34b655…2a6f
6 touches
3 conflicts
0x4d7057a9…1c18
0x34b655…2a6f
4 touches
1 conflict
0x5e782d17…5317
0x34b655…2a6f
4 touches
1 conflict
0xbb7e1b5f…1212
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 0x3c7520fc9a…f89ca3
Audit this contract →
← previous block·next block →recent activity