Block #71,742,365

← previous blocknext block →recent activity

Analyzing

Block #71,742,365

36 transactions · 19 stateful · 2026-05-01 14:00:29 UTC

Parallelism

83/100

Blocked

53%

Avg conflicts / tx

0.64

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

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

0x59bce3df…bc3b

0xd32edf…ff58

7 touches
6 conflicts

0xe54a1f6f…18f2

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x438cf5f6…f077

0x2a68ba…90c5

4 touches
1 conflict

0x37d49489…9309

0x34b655…2a6f

4 touches
1 conflict

0x3df3de0d…cd8b

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