← previous blocknext block →recent activity

Analyzing

Block #72,498,713

37 transactions · 22 stateful · 2026-05-05 02:04:42 UTC

Parallelism

78/100

Blocked

55%

Avg conflicts / tx

0.92

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #72,498,713  ·  37 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

0x064ae548…fb43

0xd32edf…ff58

15 touches
28 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x56a919c4…ab49

0xee8c0e…1242

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x8571fbdb…345a

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

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 0x064ae548e8…62fb43

← previous block·next block →recent activity