Block #71,000,351

← previous blocknext block →recent activity

Analyzing

Block #71,000,351

37 transactions · 25 stateful · 2026-04-28 03:35:12 UTC

Parallelism

62/100

Blocked

80%

Avg conflicts / tx

2.86

Longest chain

14 deep

Execution timeline

did this block parallelize well?

view

block #71,000,351  ·  37 txs across 14 waves  ·  depth 14
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

wave w13

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

0x6e5c5e46…ec4c

0xd32edf…ff58

27 touches
91 conflicts

0x00000000…0002

0xb857c1…9be1

10 touches
10 conflicts

0x00000000…0000

0x659bd0…a9da

6 touches
3 conflicts

0x7e28e55c…d05c

0x754704…b603

6 touches
3 conflicts

0xcce2fd99…a8eb

0x3bd359…433a

6 touches
3 conflicts

0x00000000…0002

0x659bd0…a9da

6 touches
3 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

6 touches
3 conflicts

0xc3c8642a…7da5

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

91 conflicts on slot 0x6e5c5e46f7…0bec4c

← previous block·next block →recent activity