← previous blocknext block →recent activity

Analyzing

Block #72,458,102

9 transactions · 7 stateful · 2026-05-04 21:34:23 UTC

Parallelism

78/100

Blocked

14%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,458,102  ·  9 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

0xd6f26bec…530e

0x065c9d…c394

3 touches
1 conflict

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0x3e6ccbb7…1a83

0x0a3323…0a3c

2 touches
0 conflicts

0xb1632c2f…d991

0x0a3323…0a3c

2 touches
0 conflicts

0xdd6693d2…d424

0x0a3323…0a3c

2 touches
0 conflicts

0xff393f19…4dd2

0x0a3323…0a3c

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 0xd6f26bec8e…6f530e

← previous block·next block →recent activity