← previous blocknext block →recent activity

Analyzing

Block #81,878,697

13 transactions · 9 stateful · 2026-06-17 12:49:23 UTC

Parallelism

77/100

Blocked

22%

Avg conflicts / tx

0.23

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #81,878,697  ·  13 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

0x95b76c4f…c6f6

0x34b655…2a6f

4 touches
1 conflict

0x9aff966c…53ce

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x7506443a…4820

0x34b655…2a6f

4 touches
1 conflict

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0xfab1627b…b819

0x34b655…2a6f

4 touches
1 conflict

0x12f3bc96…8d5b

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 0x95b76c4fa5…1bc6f6

← previous block·next block →recent activity