← previous blocknext block →recent activity

Analyzing

Block #72,571,144

10 transactions · 9 stateful · 2026-05-05 10:06:56 UTC

Parallelism

60/100

Blocked

44%

Avg conflicts / tx

0.9

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,571,144  ·  10 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

0x40a72cc1…d1d5

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x93afca4c…b47e

0x1b6862…e19c

6 touches
3 conflicts

0x7b810964…ab26

0x065c9d…c394

4 touches
1 conflict

0xa0c96af9…a5e7

0x065c9d…c394

4 touches
1 conflict

0xf35c67d6…3967

0x065c9d…c394

4 touches
1 conflict

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: 0xd32edf66…9fff58

6 conflicts on slot 0x40a72cc107…0dd1d5

← previous block·next block →recent activity