← previous blocknext block →recent activity

Analyzing

Block #86,929,910

16 transactions · 16 stateful · 2026-07-10 22:39:17 UTC

Parallelism

75/100

Blocked

50%

Avg conflicts / tx

0.63

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,929,910  ·  16 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

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x90e113f8…c8f9

0xc8689a…ee79

4 touches
1 conflict

0xce827910…ff22

0x065c9d…c394

4 touches
1 conflict

0xfadc118d…5d64

0x34b655…2a6f

4 touches
1 conflict

0x2efac4f6…3abf

0x34b655…2a6f

4 touches
1 conflict

0x5f251b96…6054

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 0x0733be30d6…38112f

← previous block·next block →recent activity