← previous blocknext block →recent activity

Analyzing

Block #82,641,196

15 transactions · 12 stateful · 2026-06-21 01:39:29 UTC

Parallelism

87/100

Blocked

17%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #82,641,196  ·  15 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

0x517d35c7…f359

0x34b655…2a6f

4 touches
1 conflict

0x9afe9e8c…cebe

0x34b655…2a6f

4 touches
1 conflict

0xa8667a2e…b5e2

0x34b655…2a6f

4 touches
1 conflict

0xaa48195d…ffee

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x04d5d8ee…4225

0x34b655…2a6f

4 touches
1 conflict

0x05edf2cf…ac3c

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

1 conflict on slot 0x517d35c7d4…69f359

← previous block·next block →recent activity