← previous blocknext block →recent activity

Analyzing

Block #83,400,294

22 transactions · 19 stateful · 2026-06-24 14:13:14 UTC

Parallelism

68/100

Blocked

47%

Avg conflicts / tx

0.91

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #83,400,294  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xe99d8e68…a16e

0x34b655…2a6f

10 touches
10 conflicts

0x901d9f30…67a4

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x967b4a40…7a78

0x34b655…2a6f

5 touches
3 conflicts

0x757b0543…e087

0x34b655…2a6f

4 touches
1 conflict

0x9b58e20f…2dd9

0x34b655…2a6f

4 touches
1 conflict

0x9c7571b3…9605

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

10 conflicts on slot 0xe99d8e683a…2ea16e

← previous block·next block →recent activity