← previous blocknext block →recent activity

Analyzing

Block #73,343,801

31 transactions · 25 stateful · 2026-05-08 23:51:59 UTC

Parallelism

71/100

Blocked

56%

Avg conflicts / tx

1.48

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,343,801  ·  31 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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…003d

0x065c9d…c394

16 touches
28 conflicts

0xc3f9c17f…4d82

0xd32edf…ff58

11 touches
15 conflicts

0xf537eaa0…73c8

0x065c9d…c394

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x3293a887…4402

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002d

0x1b6862…e19c

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: 0x065c9d28…a9c394

28 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity