← previous blocknext block →recent activity

Analyzing

Block #83,413,313

31 transactions · 27 stateful · 2026-06-24 15:40:13 UTC

Parallelism

58/100

Blocked

63%

Avg conflicts / tx

2.32

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #83,413,313  ·  31 txs across 13 waves  ·  depth 13
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

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

18 touches
36 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

14 touches
21 conflicts

0x9c4bf061…1101

0x34b655…2a6f

8 touches
8 conflicts

0xffc2f21e…b393

0x34b655…2a6f

8 touches
6 conflicts

0x03fb27fd…0c06

0x34b655…2a6f

6 touches
3 conflicts

0x0462262d…a368

0x34b655…2a6f

6 touches
3 conflicts

0x4418945a…98e0

0x34b655…2a6f

6 touches
3 conflicts

0xdf37a93d…879b

0x34b655…2a6f

6 touches
3 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

36 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity