← previous blocknext block →recent activity

Analyzing

Block #87,295,465

21 transactions · 20 stateful · 2026-07-12 15:23:07 UTC

Parallelism

67/100

Blocked

50%

Avg conflicts / tx

1.14

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #87,295,465  ·  21 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

0xc824469a…6426

0x34b655…2a6f

12 touches
15 conflicts

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0xfaef08b1…0696

0x34b655…2a6f

8 touches
6 conflicts

0x45ea7a97…bbb3

0x34b655…2a6f

8 touches
6 conflicts

0x8a35acfb…d1ad

0xb1dbf0…c0d3

5 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

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 0xc824469a90…af6426

← previous block·next block →recent activity