← previous blocknext block →recent activity

Analyzing

Block #73,867,994

15 transactions · 11 stateful · 2026-05-11 10:16:30 UTC

Parallelism

53/100

Blocked

64%

Avg conflicts / tx

1.53

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,867,994  ·  15 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

0x17c6e677…8faa

0xd32edf…ff58

13 touches
21 conflicts

0x05eea3e3…5846

0x2a68ba…90c5

6 touches
3 conflicts

0x4cb2b152…2e00

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0018

0x1b6862…e19c

4 touches
1 conflict

0x62f88366…855f

0x065c9d…c394

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0028

0x1b6862…e19c

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: 0xd32edf66…9fff58

21 conflicts on slot 0x17c6e677af…e98faa

← previous block·next block →recent activity