← previous blocknext block →recent activity

Analyzing

Block #86,741,647

18 transactions · 16 stateful · 2026-07-10 01:40:59 UTC

Parallelism

78/100

Blocked

44%

Avg conflicts / tx

0.61

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,741,647  ·  18 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

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xdb6aaff6…d579

0x34b655…2a6f

6 touches
3 conflicts

0x0bd95eb4…e562

0x34b655…2a6f

4 touches
1 conflict

0x1bee5aea…5f61

0x34b655…2a6f

4 touches
1 conflict

0x23ef1567…8f31

0x34b655…2a6f

4 touches
1 conflict

0x440235f2…c9bb

0x34b655…2a6f

4 touches
1 conflict

0x5d863b2f…bd28

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 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity