← previous blocknext block →recent activity

Analyzing

Block #82,712,448

19 transactions · 16 stateful · 2026-06-21 09:36:07 UTC

Parallelism

74/100

Blocked

44%

Avg conflicts / tx

0.79

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #82,712,448  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x22e0cc1d…ad04

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0xc68d6f14…bdde

0x34b655…2a6f

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

2 touches
0 conflicts

0x40970e69…da50

0x69df8a…6292

2 touches
0 conflicts

0x8cf3d245…1d0d

0x69df8a…6292

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity