← previous blocknext block →recent activity

Analyzing

Block #82,018,742

65 transactions · 17 stateful · 2026-06-18 04:24:57 UTC

Parallelism

89/100

Blocked

47%

Avg conflicts / tx

0.37

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #82,018,742  ·  65 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

0xf6476f21…3580

0x34b655…2a6f

14 touches
21 conflicts

0x1086ec16…1a17

0x34b655…2a6f

6 touches
3 conflicts

0x6b47245e…a342

0x34b655…2a6f

6 touches
3 conflicts

0x7506443a…4820

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x3b10542d…908f

0x34b655…2a6f

4 touches
1 conflict

0x9c7ce5c3…2a4e

0x34b655…2a6f

4 touches
1 conflict

0xc08384da…ecb7

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

21 conflicts on slot 0xf6476f21e7…f83580

← previous block·next block →recent activity