← previous blocknext block →recent activity

Analyzing

Block #73,214,560

31 transactions · 25 stateful · 2026-05-08 09:32:08 UTC

Parallelism

74/100

Blocked

60%

Avg conflicts / tx

1.45

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,214,560  ·  31 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xd5ee3135…b90b

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…0002

0xab3526…fa38

8 touches
6 conflicts

0x00000000…001b

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002b

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0xe937b6bc…8a57

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

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

28 conflicts on slot 0xd5ee313534…8bb90b

← previous block·next block →recent activity