← previous blocknext block →recent activity

Analyzing

Block #86,244,540

17 transactions · 15 stateful · 2026-07-07 18:17:07 UTC

Parallelism

65/100

Blocked

47%

Avg conflicts / tx

1.06

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,244,540  ·  17 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xa678cb89…4abd

0x34b655…2a6f

5 touches
3 conflicts

0x32409e80…a396

0x34b655…2a6f

4 touches
1 conflict

0x36c2ebc4…e577

0x34b655…2a6f

4 touches
1 conflict

0x4c22021d…f8a7

0x34b655…2a6f

4 touches
1 conflict

0x53cccb07…d7f0

0x34b655…2a6f

4 touches
1 conflict

0x548145a9…cfce

0x34b655…2a6f

4 touches
1 conflict

0x6637e421…af93

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