← previous blocknext block →recent activity

Analyzing

Block #83,636,300

18 transactions · 17 stateful · 2026-06-25 16:28:27 UTC

Parallelism

50/100

Blocked

59%

Avg conflicts / tx

1.78

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #83,636,300  ·  18 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

0x3405238a…68b6

0x34b655…2a6f

14 touches
21 conflicts

0xcd63138b…63d9

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x63f3ab23…476d

0x34b655…2a6f

8 touches
6 conflicts

0xf4a79d55…3f4f

0x34b655…2a6f

7 touches
6 conflicts

0x03fb27fd…0c06

0x34b655…2a6f

6 touches
3 conflicts

0x2fdfa032…139c

0x34b655…2a6f

6 touches
3 conflicts

0xd4702f73…926c

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

21 conflicts on slot 0x3405238a6d…6268b6

← previous block·next block →recent activity