← previous blocknext block →recent activity
Analyzing
Block #85,160,671
11 transactions · 11 stateful · 2026-07-02 17:52:35 UTC
Parallelism
82/100
Blocked
9%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,160,671 · 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb44d5376…33cc
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x370450a0…7631
0x34b655…2a6f
4 touches
1 conflict
0x63da0619…7a55
0x34b655…2a6f
4 touches
1 conflict
0x742072b0…1af8
0x34b655…2a6f
4 touches
1 conflict
0x9dfa4c21…3883
0x34b655…2a6f
4 touches
1 conflict
0x24227bc5…cb16
0x34b655…2a6f
2 touches
0 conflicts
0x2c15adb7…e65d
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 0xb44d5376ca…0b33cc
Audit this contract →
← previous block·next block →recent activity