← previous blocknext block →recent activity
Analyzing
Block #85,133,167
30 transactions · 25 stateful · 2026-07-02 14:49:20 UTC
Parallelism
80/100
Blocked
44%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,133,167 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w09w112w013w014w115w116w217w319w120w127w428w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffc2f21e…b393
0x34b655…2a6f
8 touches
6 conflicts
0x644919d7…9727
0x34b655…2a6f
7 touches
6 conflicts
0x8f549a27…9695
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xe96e3c16…a9f3
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x4d7a44a4…5ae1
0x34b655…2a6f
4 touches
1 conflict
0xa2cc62d4…69f6
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 0xffc2f21efe…ecb393
Audit this contract →
← previous block·next block →recent activity