Block #71,741,613

← previous blocknext block →recent activity

Analyzing

Block #71,741,613

34 transactions · 24 stateful · 2026-05-01 13:55:29 UTC

Parallelism

82/100

Blocked

46%

Avg conflicts / tx

0.71

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,741,613  ·  34 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

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0xf9d62963…395c

0x065c9d…c394

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0xf8f1e808…a4fd

0x34b655…2a6f

6 touches
3 conflicts

0xeebd31ac…0794

0x34b655…2a6f

6 touches
3 conflicts

0x508387de…c644

0x2a68ba…90c5

6 touches
3 conflicts

0x3df3de0d…cd8b

0x34b655…2a6f

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity