← previous blocknext block →recent activity

Analyzing

Block #86,339,913

29 transactions · 25 stateful · 2026-07-08 04:53:59 UTC

Parallelism

86/100

Blocked

24%

Avg conflicts / tx

0.28

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,339,913  ·  29 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

6 touches
3 conflicts

0x18cf3003…51d1

0x065c9d…c394

4 touches
1 conflict

0xcc8faac2…c766

0x065c9d…c394

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x0eac6378…36f4

0x34b655…2a6f

4 touches
1 conflict

0x16a8cd0c…27bd

0x34b655…2a6f

4 touches
1 conflict

0x42171967…855b

0x34b655…2a6f

4 touches
1 conflict

0x45856523…d213

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity