← previous blocknext block →recent activity

Analyzing

Block #73,795,836

39 transactions · 29 stateful · 2026-05-11 02:15:10 UTC

Parallelism

82/100

Blocked

55%

Avg conflicts / tx

1.03

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,795,836  ·  39 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

0x0ac31945…2c72

0x065c9d…c394

12 touches
15 conflicts

0x3e733ae4…4598

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0x2325f993…aeb0

0xd32edf…ff58

7 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

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: 0x065c9d28…a9c394

15 conflicts on slot 0x0ac3194537…8f2c72

← previous block·next block →recent activity