← previous blocknext block →recent activity

Analyzing

Block #72,286,223

16 transactions · 15 stateful · 2026-05-04 02:28:39 UTC

Parallelism

88/100

Blocked

13%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,286,223  ·  16 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xe4c28306…b1dd

0xd32edf…ff58

3 touches
1 conflict

0xd29de53c…a369

0x065c9d…c394

3 touches
1 conflict

0xe70bdebb…626e

0x065c9d…c394

3 touches
1 conflict

0x4d8766fd…f1c6

0x000000…012a

2 touches
0 conflicts

0x78eb0de5…1db2

0x01bff4…1071

2 touches
0 conflicts

0x7d96cf5d…df0f

0x01bff4…1071

2 touches
0 conflicts

0xa1e7323c…ca02

0x01bff4…1071

2 touches
0 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: 0x065c9d28…a9c394

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity