← previous blocknext block →recent activity

Analyzing

Block #72,284,821

15 transactions · 13 stateful · 2026-05-04 02:19:13 UTC

Parallelism

73/100

Blocked

38%

Avg conflicts / tx

0.8

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,284,821  ·  15 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xbbee74c2…567a

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0xa36ce883…837d

0x065c9d…c394

3 touches
1 conflict

0x00000000…0018

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0028

0x1b6862…e19c

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

6 conflicts on slot 0xbbee74c2e7…6e567a

← previous block·next block →recent activity