← previous blocknext block →recent activity

Analyzing

Block #86,803,130

26 transactions · 19 stateful · 2026-07-10 08:31:35 UTC

Parallelism

77/100

Blocked

47%

Avg conflicts / tx

0.54

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,803,130  ·  26 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

0x8d888c90…5479

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xfd42a6b9…4c81

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x6638e124…bc7f

0x34b655…2a6f

4 touches
1 conflict

0x793aa64d…b09c

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 0x8d888c9003…aa5479

← previous block·next block →recent activity