← previous blocknext block →recent activity

Analyzing

Block #73,911,758

19 transactions · 17 stateful · 2026-05-11 15:07:56 UTC

Parallelism

42/100

Blocked

59%

Avg conflicts / tx

2.89

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #73,911,758  ·  19 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x00000000…0000

0x3e1523…94aa

22 touches
55 conflicts

0x00000000…0001

0x3e1523…94aa

22 touches
55 conflicts

0x00000000…0003

0x3e1523…94aa

22 touches
55 conflicts

0xed385e36…0251

0x7b2728…7777

22 touches
55 conflicts

0xe4b00f4b…34c0

0x3bd359…433a

22 touches
55 conflicts

0xbd7e37a9…9eb5

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

2 touches
0 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: 0x3e1523b2…8994aa

55 conflicts on slot 0x0000000000…000000

← previous block·next block →recent activity