Block #71,090,358

← previous blocknext block →recent activity

Analyzing

Block #71,090,358

25 transactions · 23 stateful · 2026-04-28 13:34:33 UTC

Parallelism

76/100

Blocked

39%

Avg conflicts / tx

0.64

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,090,358  ·  25 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xf88ecf3c…f023

0xd32edf…ff58

7 touches
6 conflicts

0x11f25e19…8bb1

0x34b655…2a6f

6 touches
3 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

6 touches
3 conflicts

0x21d22421…0b7a

0x34b655…2a6f

6 touches
3 conflicts

0x24bb3c45…0377

0x34b655…2a6f

6 touches
3 conflicts

0x262a793c…1d06

0x34b655…2a6f

6 touches
3 conflicts

0x3b74ae43…a235

0x34b655…2a6f

6 touches
3 conflicts

0x3c35979a…975d

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: 0xd32edf66…9fff58

6 conflicts on slot 0xf88ecf3c65…32f023

← previous block·next block →recent activity