← previous blocknext block →recent activity

Analyzing

Block #83,453,364

27 transactions · 22 stateful · 2026-06-24 20:07:46 UTC

Parallelism

67/100

Blocked

41%

Avg conflicts / tx

0.85

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #83,453,364  ·  27 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xda5e0705…ecb9

0x34b655…2a6f

10 touches
10 conflicts

0xffc2f21e…b393

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

8 touches
6 conflicts

0x8ae827f1…aa36

0x34b655…2a6f

6 touches
3 conflicts

0xee7978e9…2869

0x34b655…2a6f

5 touches
3 conflicts

0xffb1ee54…7c2c

0x34b655…2a6f

5 touches
3 conflicts

0x7a2b18bf…d24e

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 0xda5e0705c4…a5ecb9

← previous block·next block →recent activity