← previous blocknext block →recent activity

Analyzing

Block #72,288,054

27 transactions · 20 stateful · 2026-05-04 02:40:58 UTC

Parallelism

70/100

Blocked

55%

Avg conflicts / tx

1.22

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #72,288,054  ·  27 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

0x11866f78…1264

0xd32edf…ff58

15 touches
28 conflicts

0x749e5faa…ab50

0x065c9d…c394

5 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0018

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0028

0x1b6862…e19c

4 touches
1 conflict

0x59658b83…2225

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

28 conflicts on slot 0x11866f787c…f81264

← previous block·next block →recent activity