← previous blocknext block →recent activity

Analyzing

Block #86,632,393

20 transactions · 19 stateful · 2026-07-09 13:30:08 UTC

Parallelism

75/100

Blocked

42%

Avg conflicts / tx

0.6

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,632,393  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x7523ad90…2ba5

0x34b655…2a6f

6 touches
3 conflicts

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x3483ab79…8ed3

0x34b655…2a6f

4 touches
1 conflict

0x63c900f4…2600

0x34b655…2a6f

4 touches
1 conflict

0x67eb9f2d…885a

0x34b655…2a6f

4 touches
1 conflict

0x70df5d25…3fd5

0x34b655…2a6f

4 touches
1 conflict

0x7a12283f…b18a

0x69df8a…6292

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

3 conflicts on slot 0x7523ad907c…052ba5

← previous block·next block →recent activity