Block #71,742,438

← previous blocknext block →recent activity

Analyzing

Block #71,742,438

27 transactions · 25 stateful · 2026-05-01 14:00:58 UTC

Parallelism

81/100

Blocked

52%

Avg conflicts / tx

1.04

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,742,438  ·  27 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0xbca83ad5…c740

0xd32edf…ff58

9 touches
10 conflicts

0x6af306bb…2e81

0x3bd359…433a

6 touches
3 conflicts

0xce8bbe33…b72e

0x3bd359…433a

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0xf91b744e…9117

0x754704…b603

6 touches
3 conflicts

0x00000000…001d

0x1b6862…e19c

4 touches
1 conflict

0xcb45d9d6…cb85

0x1b6862…e19c

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity