← previous blocknext block →recent activity

Analyzing

Block #71,741,065

18 transactions · 17 stateful · 2026-05-01 13:51:48 UTC

Parallelism

67/100

Blocked

47%

Avg conflicts / tx

1.06

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,741,065  ·  18 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

0x908d4442…2c4b

0x34b655…2a6f

6 touches
3 conflicts

0xcbad3868…f129

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xf3981be5…2c47

0x34b655…2a6f

6 touches
3 conflicts

0xf853eb8e…4027

0x34b655…2a6f

6 touches
3 conflicts

0x37d49489…9309

0x34b655…2a6f

6 touches
3 conflicts

0xdbfbf6e0…a619

0xd32edf…ff58

5 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