← previous blocknext block →recent activity

Analyzing

Block #83,493,690

40 transactions · 33 stateful · 2026-06-25 00:36:51 UTC

Parallelism

65/100

Blocked

70%

Avg conflicts / tx

2.52

Longest chain

14 deep

Execution timeline

did this block parallelize well?

view

block #83,493,690  ·  40 txs across 14 waves  ·  depth 14
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

wave w13

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

20 touches
45 conflicts

0x889a1747…a7ce

0x34b655…2a6f

14 touches
21 conflicts

0xa02e5cdd…76b8

0x34b655…2a6f

12 touches
15 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x45866eab…abfa

0x34b655…2a6f

8 touches
6 conflicts

0x8d6cfd93…6eb6

0x34b655…2a6f

8 touches
6 conflicts

0xeb0b1d43…9559

0x34b655…2a6f

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

45 conflicts on slot 0xe99d8e683a…2ea16e

← previous block·next block →recent activity