← previous blocknext block →recent activity

Analyzing

Block #85,179,837

20 transactions · 19 stateful · 2026-07-02 20:00:11 UTC

Parallelism

65/100

Blocked

42%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #85,179,837  ·  20 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0xb44564d6…bb43

0x34b655…2a6f

6 touches
3 conflicts

0xd63e616b…a07d

0x34b655…2a6f

6 touches
3 conflicts

0x4b33144c…3890

0x34b655…2a6f

4 touches
1 conflict

0x51a914cf…a822

0x34b655…2a6f

4 touches
1 conflict

0x548145a9…cfce

0x34b655…2a6f

4 touches
1 conflict

0x58603063…4ef0

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity