← previous blocknext block →recent activity

Analyzing

Block #72,233,868

27 transactions · 22 stateful · 2026-05-03 20:36:45 UTC

Parallelism

67/100

Blocked

55%

Avg conflicts / tx

1.56

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #72,233,868  ·  27 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xcef1a5bf…d478

0xd32edf…ff58

17 touches
36 conflicts

0xd025d7d7…f05a

0x3bd359…433a

6 touches
3 conflicts

0xd996735f…8735

0x1b6862…e19c

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001f

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002f

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

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

36 conflicts on slot 0xcef1a5bf00…09d478

← previous block·next block →recent activity