← previous blocknext block →recent activity

Analyzing

Block #72,284,215

23 transactions · 22 stateful · 2026-05-04 02:15:08 UTC

Parallelism

74/100

Blocked

59%

Avg conflicts / tx

1.22

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,284,215  ·  23 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xbad68552…e6bf

0x34b655…2a6f

12 touches
15 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

8 touches
6 conflicts

0x2877f440…c2c8

0x34b655…2a6f

8 touches
6 conflicts

0x3254d19b…f714

0x34b655…2a6f

8 touches
6 conflicts

0x414e9446…4b59

0x34b655…2a6f

8 touches
6 conflicts

0x65e795ca…0320

0x34b655…2a6f

8 touches
6 conflicts

0x904fc3c0…00ec

0x34b655…2a6f

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

15 conflicts on slot 0xbad6855239…f0e6bf

← previous block·next block →recent activity