← previous blocknext block →recent activity

Analyzing

Block #72,287,968

31 transactions · 23 stateful · 2026-05-04 02:40:24 UTC

Parallelism

74/100

Blocked

48%

Avg conflicts / tx

1.16

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #72,287,968  ·  31 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

0x835de5ea…3551

0xd32edf…ff58

15 touches
28 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x6af306bb…2e81

0x3bd359…433a

6 touches
3 conflicts

0x1c354dc0…96de

0x754704…b603

6 touches
3 conflicts

0xf91b744e…9117

0x754704…b603

6 touches
3 conflicts

0x0f28fb99…3d29

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

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: 0xd32edf66…9fff58

28 conflicts on slot 0x835de5eaf3…b13551

← previous block·next block →recent activity