← previous blocknext block →recent activity

Analyzing

Block #71,696,511

17 transactions · 16 stateful · 2026-05-01 08:55:11 UTC

Parallelism

88/100

Blocked

31%

Avg conflicts / tx

0.29

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,696,511  ·  17 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

0x846f2172…fd54

0x0555e3…2b9c

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x489cb750…7069

0x065c9d…c394

4 touches
1 conflict

0x4cb2b152…2e00

0x065c9d…c394

4 touches
1 conflict

0x46cb45de…a566

0x188d58…ea8e

4 touches
1 conflict

0x46cb45de…a567

0x188d58…ea8e

4 touches
1 conflict

0x8c49c85c…ee96

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

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: 0x0555e30d…0d2b9c

1 conflict on slot 0x846f21722e…fdfd54

← previous block·next block →recent activity