← previous blocknext block →recent activity

Analyzing

Block #72,498,718

30 transactions · 26 stateful · 2026-05-05 02:04:44 UTC

Parallelism

60/100

Blocked

65%

Avg conflicts / tx

1.47

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #72,498,718  ·  30 txs across 12 waves  ·  depth 12
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

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

0xffe431af…8faa

0x065c9d…c394

12 touches
15 conflicts

0xd2448c70…71b3

0xd32edf…ff58

11 touches
15 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0xf8480e2a…dff2

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002c

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

15 conflicts on slot 0xffe431af56…838faa

← previous block·next block →recent activity