← previous blocknext block →recent activity

Analyzing

Block #86,153,013

21 transactions · 17 stateful · 2026-07-07 08:05:58 UTC

Parallelism

71/100

Blocked

47%

Avg conflicts / tx

0.76

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,153,013  ·  21 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

0xea02471d…1542

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x94dabb65…43a3

0x34b655…2a6f

6 touches
3 conflicts

0x9b78cb10…2a23

0x34b655…2a6f

6 touches
3 conflicts

0x6637e421…af93

0x34b655…2a6f

4 touches
1 conflict

0x6762cac2…3fb0

0x34b655…2a6f

4 touches
1 conflict

0xb245fe36…d765

0x34b655…2a6f

4 touches
1 conflict

0xded5ec0c…f0fc

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

10 conflicts on slot 0xea02471df2…601542

← previous block·next block →recent activity