← previous blocknext block →recent activity

Analyzing

Block #71,176,531

8 transactions · 8 stateful · 2026-04-28 23:08:32 UTC

Parallelism

63/100

Blocked

25%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,176,531  ·  8 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x00000000…0004

0xd0f8a6…badc

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x2d10a2de…811f

0x065c9d…c394

6 touches
3 conflicts

0x8b29bbcd…3ad9

0x065c9d…c394

6 touches
3 conflicts

0xf201dcc4…5c44

0x065c9d…c394

5 touches
3 conflicts

0x77a88986…e5b8

0x065c9d…c394

5 touches
3 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

4 touches
1 conflict

0x92d610a6…9a40

0x2a68ba…90c5

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: 0xd0f8a642…83badc

3 conflicts on slot 0x0000000000…000004

← previous block·next block →recent activity