← previous blocknext block →recent activity

Analyzing

Block #82,273,464

20 transactions · 19 stateful · 2026-06-19 08:43:44 UTC

Parallelism

65/100

Blocked

47%

Avg conflicts / tx

1.25

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #82,273,464  ·  20 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

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0xd99b3b64…1c95

0x34b655…2a6f

6 touches
3 conflicts

0xedcf2991…8551

0x34b655…2a6f

6 touches
3 conflicts

0x6f58168d…ea24

0x34b655…2a6f

6 touches
3 conflicts

0x5540f956…69e8

0x065c9d…c394

6 touches
3 conflicts

0xbde30d77…b032

0x34b655…2a6f

5 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity