Block #71,090,538

← previous blocknext block →recent activity

Analyzing

Block #71,090,538

23 transactions · 18 stateful · 2026-04-28 13:35:46 UTC

Parallelism

65/100

Blocked

50%

Avg conflicts / tx

1.3

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #71,090,538  ·  23 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x810357da…a42a

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x1045386d…cb86

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0018

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0028

0x1b6862…e19c

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

28 conflicts on slot 0x810357dafe…49a42a

← previous block·next block →recent activity