← previous blocknext block →recent activity
Analyzing
Block #85,177,932
10 transactions · 9 stateful · 2026-07-02 19:47:29 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,177,932 · 10 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
3w04w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x3ea25e92…a36d
0x34b655…2a6f
2 touches
0 conflicts
0x423ae7f8…c929
0x34b655…2a6f
2 touches
0 conflicts
0x44429a9b…771d
0x34b655…2a6f
2 touches
0 conflicts
0x5ad3280d…16bb
0x34b655…2a6f
2 touches
0 conflicts
0x6167486f…db40
0x34b655…2a6f
2 touches
0 conflicts
0x765cd07a…1018
0x34b655…2a6f
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity