← previous blocknext block →recent activity

Analyzing

Block #72,288,017

9 transactions · 6 stateful · 2026-05-04 02:40:43 UTC

Parallelism

67/100

Blocked

33%

Avg conflicts / tx

0.22

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,288,017  ·  9 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xc8c5c62c…45f4

0x065c9d…c394

4 touches
1 conflict

0xc3c8642a…7da5

0x2a68ba…90c5

4 touches
1 conflict

0x7c3a57a4…ee09

0x065c9d…c394

4 touches
1 conflict

0x7710b99f…d8d7

0x065c9d…c394

3 touches
1 conflict

0x24968e6d…0132

0x065c9d…c394

2 touches
0 conflicts

0x7d54cee3…7403

0x065c9d…c394

2 touches
0 conflicts

0xad2fc9f8…e9ef

0x065c9d…c394

2 touches
0 conflicts

0x00f7e3b7…e015

0x188d58…ea8e

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 0xc8c5c62cf0…2745f4

← previous block·next block →recent activity