Block #71,742,355

← previous blocknext block →recent activity

Analyzing

Block #71,742,355

16 transactions · 10 stateful · 2026-05-01 14:00:25 UTC

Parallelism

81/100

Blocked

30%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,742,355  ·  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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x6dd62d2b…f17e

0x34b655…2a6f

4 touches
1 conflict

0xa433ef1c…2a52

0x34b655…2a6f

4 touches
1 conflict

0x408e66bb…3d6b

0x34b655…2a6f

4 touches
1 conflict

0xf3981be5…2c47

0x34b655…2a6f

4 touches
1 conflict

0xfd784183…67bb

0x34b655…2a6f

4 touches
1 conflict

0x3cd3ba79…b722

0xd32edf…ff58

3 touches
1 conflict

0x4dd1db39…a994

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity