← previous blocknext block →recent activity

Analyzing

Block #71,239,543

26 transactions · 18 stateful · 2026-04-29 06:07:37 UTC

Parallelism

73/100

Blocked

56%

Avg conflicts / tx

0.65

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #71,239,543  ·  26 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

0x0a809ce1…7894

0x34b655…2a6f

6 touches
3 conflicts

0x89999c15…fdac

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x8a35acfb…d1ae

0x8d66a4…3095

6 touches
3 conflicts

0x96504a63…52d2

0x8d66a4…3095

6 touches
3 conflicts

0x00000000…0002

0xb857c1…9be1

6 touches
3 conflicts

0x374426df…f445

0xc8689a…ee79

6 touches
3 conflicts

0x908d4442…2c4b

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

3 conflicts on slot 0x0a809ce130…5f7894

← previous block·next block →recent activity