← previous blocknext block →recent activity

Analyzing

Block #72,233,819

8 transactions · 8 stateful · 2026-05-03 20:36:26 UTC

Parallelism

75/100

Blocked

13%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,233,819  ·  8 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

0xedc24e9e…1cd3

0x34b655…2a6f

4 touches
1 conflict

0x1c389468…6b0e

0x34b655…2a6f

4 touches
1 conflict

0xc1a4c088…e828

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x43a4c528…fbae

0x065c9d…c394

2 touches
0 conflicts

0x61ce6b7c…e9ea

0x065c9d…c394

2 touches
0 conflicts

0x6b29cd58…312e

0x065c9d…c394

2 touches
0 conflicts

0x00000000…009a

0x16f70c…c3dd

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: 0x34b6552d…112a6f

1 conflict on slot 0xedc24e9eb8…7f1cd3

← previous block·next block →recent activity