← previous blocknext block →recent activity

Analyzing

Block #72,286,253

7 transactions · 6 stateful · 2026-05-04 02:28:51 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,286,253  ·  7 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

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0xdefadca2…5f30

0x065c9d…c394

4 touches
1 conflict

0x1494b20d…1e86

0x065c9d…c394

2 touches
0 conflicts

0x314c2ff2…6f4a

0x065c9d…c394

2 touches
0 conflicts

0x3dea172b…b046

0x065c9d…c394

2 touches
0 conflicts

0xa3dc5c61…c0c3

0x065c9d…c394

2 touches
0 conflicts

0xdc5ed8c2…db16

0x065c9d…c394

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