← previous blocknext block →recent activity

Analyzing

Block #72,097,949

27 transactions · 23 stateful · 2026-05-03 05:27:47 UTC

Parallelism

78/100

Blocked

57%

Avg conflicts / tx

1.04

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,097,949  ·  27 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

0xe2acaf6a…49e8

0xd32edf…ff58

9 touches
10 conflicts

0xbad68552…e6bf

0x34b655…2a6f

8 touches
6 conflicts

0x8e66c393…c9a2

0x34b655…2a6f

6 touches
3 conflicts

0xadac4a86…c2bc

0x34b655…2a6f

6 touches
3 conflicts

0xce8bbe33…b72e

0x3bd359…433a

6 touches
3 conflicts

0x44102a6e…2ea1

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x6af306bb…2e81

0x3bd359…433a

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

10 conflicts on slot 0xe2acaf6a34…1349e8

← previous block·next block →recent activity