← previous blocknext block →recent activity

Analyzing

Block #83,671,789

12 transactions · 11 stateful · 2026-06-25 20:25:12 UTC

Parallelism

83/100

Blocked

18%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #83,671,789  ·  12 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x86977b3d…a9c4

0x34b655…2a6f

4 touches
1 conflict

0xe99d8e68…a16e

0x34b655…2a6f

4 touches
1 conflict

0x132cd2d6…abe6

0x34b655…2a6f

4 touches
1 conflict

0x18ca6535…87c1

0x34b655…2a6f

4 touches
1 conflict

0x6b47245e…a342

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x8e5cc690…b06b

0x34b655…2a6f

2 touches
0 conflicts

0x9985dbdd…c2a3

0x34b655…2a6f

2 touches
0 conflicts

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

1 conflict on slot 0x86977b3d38…81a9c4

← previous block·next block →recent activity