← previous blocknext block →recent activity

Analyzing

Block #86,785,196

18 transactions · 16 stateful · 2026-07-10 06:31:48 UTC

Parallelism

78/100

Blocked

50%

Avg conflicts / tx

0.72

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,785,196  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0x1369a917…8327

0x34b655…2a6f

4 touches
1 conflict

0x1bce8046…f6ca

0x34b655…2a6f

4 touches
1 conflict

0x226b4d09…8113

0x34b655…2a6f

4 touches
1 conflict

0x2b268fa9…eba2

0x34b655…2a6f

4 touches
1 conflict

0x3750b746…5a9e

0x34b655…2a6f

4 touches
1 conflict

0x59af9e63…3406

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 0xac2a02739b…81721b

← previous block·next block →recent activity