← previous blocknext block →recent activity
Analyzing
Block #85,182,903
11 transactions · 8 stateful · 2026-07-02 20:20:39 UTC
Parallelism
82/100
Blocked
25%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,182,903 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51087f5a…61f7
0x34b655…2a6f
4 touches
1 conflict
0x88451e43…5a97
0x34b655…2a6f
4 touches
1 conflict
0xd895ee0b…d301
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x1d320438…987b
0x40c49f…2af0
2 touches
0 conflicts
0x38cc9215…d119
0x40c49f…2af0
2 touches
0 conflicts
0xbfaf490a…cdcf
0x40c49f…2af0
2 touches
0 conflicts
0xf08b254b…1223
0x40c49f…2af0
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
1 conflict on slot 0x51087f5abf…f061f7
Audit this contract →
← previous block·next block →recent activity