← previous blocknext block →recent activity

Analyzing

Block #72,400,215

13 transactions · 10 stateful · 2026-05-04 15:08:39 UTC

Parallelism

85/100

Blocked

20%

Avg conflicts / tx

0.23

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,400,215  ·  13 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

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0x4ba1fda1…2acc

0x065c9d…c394

2 touches
0 conflicts

0x7bdc89f2…eaec

0x065c9d…c394

2 touches
0 conflicts

0xdaa9a79c…12d8

0x065c9d…c394

2 touches
0 conflicts

0xf35c67d6…3967

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