Block #71,239,264

← previous blocknext block →recent activity

Analyzing

Block #71,239,264

15 transactions · 15 stateful · 2026-04-29 06:05:46 UTC

Parallelism

53/100

Blocked

40%

Avg conflicts / tx

1.2

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #71,239,264  ·  15 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xf853eb8e…4027

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x7cbd466f…1700

0x34b655…2a6f

8 touches
6 conflicts

0xd7a2b02f…1da4

0x34b655…2a6f

8 touches
6 conflicts

0xe54a1f6f…18f2

0x34b655…2a6f

8 touches
6 conflicts

0x23951077…539b

0x34b655…2a6f

6 touches
3 conflicts

0x77905798…fe3d

0x34b655…2a6f

6 touches
3 conflicts

0xc3aacf13…6b3d

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

10 conflicts on slot 0xf853eb8e72…d84027

← previous block·next block →recent activity