← previous blocknext block →recent activity

Analyzing

Block #71,289,697

16 transactions · 11 stateful · 2026-04-29 11:41:23 UTC

Parallelism

81/100

Blocked

27%

Avg conflicts / tx

0.19

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,289,697  ·  16 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

0x00000000…001c

0x1b6862…e19c

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xdc281e7b…d41d

0x5afd3e…7620

4 touches
1 conflict

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0xcb45d9d6…cb84

0x1b6862…e19c

4 touches
1 conflict

0x21795d84…8360

0x065c9d…c394

4 touches
1 conflict

0xebc3cd1a…6dc6

0xd32edf…ff58

3 touches
1 conflict

0xd41815ab…152c

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: 0x1b68626d…2de19c

1 conflict on slot 0x0000000000…00001c

← previous block·next block →recent activity