← previous blocknext block →recent activity

Analyzing

Block #71,092,212

28 transactions · 16 stateful · 2026-04-28 13:46:55 UTC

Parallelism

86/100

Blocked

56%

Avg conflicts / tx

0.54

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #71,092,212  ·  28 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

0x41755291…977f

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x18bf2a65…005d

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0004

0xd0f8a6…badc

6 touches
3 conflicts

0xc88ad484…07bc

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0002

0xb857c1…9be1

6 touches
3 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

6 touches
3 conflicts

0xd98b3c10…67b8

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: 0x065c9d28…a9c394

6 conflicts on slot 0x4175529119…79977f

← previous block·next block →recent activity