← previous blocknext block →recent activity

Analyzing

Block #73,336,282

27 transactions · 25 stateful · 2026-05-08 23:01:57 UTC

Parallelism

59/100

Blocked

60%

Avg conflicts / tx

2.15

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #73,336,282  ·  27 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

0xf537eaa0…73c8

0x065c9d…c394

14 touches
21 conflicts

0x046a928e…0012

0x2a68ba…90c5

14 touches
21 conflicts

0x6e816f2f…8470

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x6f08361d…bda6

0x065c9d…c394

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

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

21 conflicts on slot 0xf537eaa0c6…3873c8

← previous block·next block →recent activity