← previous blocknext block →recent activity

Analyzing

Block #71,744,416

23 transactions · 18 stateful · 2026-05-01 14:14:11 UTC

Parallelism

74/100

Blocked

39%

Avg conflicts / tx

0.74

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,744,416  ·  23 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x9a555477…19a8

0x754704…b603

4 touches
1 conflict

0x00000000…0004

0x63e48b…53f2

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0x3df3de0d…cd8b

0x34b655…2a6f

4 touches
1 conflict

0x408e66bb…3d6b

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: 0x34b6552d…112a6f

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity