← previous blocknext block →recent activity

Analyzing

Block #72,856,140

28 transactions · 21 stateful · 2026-05-06 17:47:02 UTC

Parallelism

71/100

Blocked

62%

Avg conflicts / tx

1.04

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #72,856,140  ·  28 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

0x78e3ec57…8bf9

0x34b655…2a6f

10 touches
10 conflicts

0x7bc0e338…ca89

0xd32edf…ff58

9 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x7f189cf6…afab

0x065c9d…c394

8 touches
6 conflicts

0xba5743c7…21c3

0x1b6862…e19c

8 touches
6 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: 0x34b6552d…112a6f

10 conflicts on slot 0x78e3ec5797…b68bf9

← previous block·next block →recent activity