← previous blocknext block →recent activity

Analyzing

Block #73,795,838

40 transactions · 30 stateful · 2026-05-11 02:15:12 UTC

Parallelism

68/100

Blocked

60%

Avg conflicts / tx

1.85

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #73,795,838  ·  40 txs across 13 waves  ·  depth 13
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

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

20 touches
45 conflicts

0x3e733ae4…4598

0x34b655…2a6f

14 touches
21 conflicts

0x8a35acfb…d1ae

0x8d66a4…3095

8 touches
6 conflicts

0x1b9e654e…0a08

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0xf2438038…5fa7

0x34b655…2a6f

8 touches
6 conflicts

0x28c180e1…f1e2

0x34b655…2a6f

6 touches
3 conflicts

0x2f7781d6…e632

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: 0x34b6552d…112a6f

45 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity