← previous blocknext block →recent activity

Analyzing

Block #71,288,923

18 transactions · 16 stateful · 2026-04-29 11:36:15 UTC

Parallelism

78/100

Blocked

31%

Avg conflicts / tx

0.44

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #71,288,923  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0x00000000…0002

0xb857c1…9be1

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x816da7dd…8587

0x065c9d…c394

4 touches
1 conflict

0x89daf25c…bc70

0x065c9d…c394

4 touches
1 conflict

0x37674bd8…8f35

0x34b655…2a6f

4 touches
1 conflict

0x5ba4db2b…2f04

0x34b655…2a6f

4 touches
1 conflict

0xf6d214b0…8abe

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity