← previous blocknext block →recent activity

Analyzing

Block #86,734,542

25 transactions · 22 stateful · 2026-07-10 00:53:28 UTC

Parallelism

72/100

Blocked

36%

Avg conflicts / tx

0.72

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #86,734,542  ·  25 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

0x02c4bb0f…f2c8

0x34b655…2a6f

4 touches
1 conflict

0x06aed19e…ca57

0x34b655…2a6f

4 touches
1 conflict

0x1929338b…cd11

0x34b655…2a6f

4 touches
1 conflict

0x6cedc82d…847a

0x34b655…2a6f

4 touches
1 conflict

0x708db6ce…a684

0x34b655…2a6f

4 touches
1 conflict

0x727fbce7…0c80

0x34b655…2a6f

4 touches
1 conflict

0x7a9a468f…e378

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