← previous blocknext block →recent activity

Analyzing

Block #73,923,916

32 transactions · 26 stateful · 2026-05-11 16:29:01 UTC

Parallelism

56/100

Blocked

69%

Avg conflicts / tx

2.91

Longest chain

14 deep

Execution timeline

did this block parallelize well?

view

block #73,923,916  ·  32 txs across 14 waves  ·  depth 14
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

wave w13

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

0xecc55752…8891

0xd32edf…ff58

25 touches
78 conflicts

0x00000000…0013

0x1b6862…e19c

18 touches
36 conflicts

0x17a7f697…dcb2

0x1b6862…e19c

18 touches
36 conflicts

0x00000000…0015

0x1b6862…e19c

18 touches
36 conflicts

0x00000000…0029

0x1b6862…e19c

16 touches
28 conflicts

0x00000000…0012

0x1b6862…e19c

16 touches
28 conflicts

0x00000000…0019

0x1b6862…e19c

16 touches
28 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

16 touches
28 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

78 conflicts on slot 0xecc557524c…238891

← previous block·next block →recent activity