← previous blocknext block →recent activity

Analyzing

Block #71,089,816

28 transactions · 20 stateful · 2026-04-28 13:30:58 UTC

Parallelism

82/100

Blocked

55%

Avg conflicts / tx

0.86

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #71,089,816  ·  28 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x1e451306…7993

0x8d66a4…3095

6 touches
3 conflicts

0x8a35acfb…d1ae

0x8d66a4…3095

6 touches
3 conflicts

0x8a35acfb…d1af

0x8d66a4…3095

6 touches
3 conflicts

0x8a35acfb…d1b0

0x8d66a4…3095

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x757254ae…d917

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: 0x34b6552d…112a6f

10 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity