← previous blocknext block →recent activity

Analyzing

Block #83,627,295

32 transactions · 14 stateful · 2026-06-25 15:28:16 UTC

Parallelism

91/100

Blocked

36%

Avg conflicts / tx

0.16

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #83,627,295  ·  32 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x967b4a40…7a78

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xe99d8e68…a16e

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x00000000…0002

0xaa7ee7…f0e4

4 touches
1 conflict

0x4f4bdabd…ffba

0x34b655…2a6f

2 touches
0 conflicts

0x62d6e82b…a750

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 0x482471adbb…39122f

← previous block·next block →recent activity