Block #71,284,214

← previous blocknext block →recent activity

Analyzing

Block #71,284,214

28 transactions · 17 stateful · 2026-04-29 11:04:57 UTC

Parallelism

68/100

Blocked

59%

Avg conflicts / tx

1.39

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #71,284,214  ·  28 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x7bd65d38…e2df

0xd32edf…ff58

17 touches
36 conflicts

0x54f9869d…c7c1

0x065c9d…c394

4 touches
1 conflict

0xc3c8642a…7da5

0x2a68ba…90c5

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x12309510…0ac2

0x000000…012a

4 touches
1 conflict

0x335a161d…fe7f

0x000000…012a

4 touches
1 conflict

0x4dd1db39…a994

0x188d58…ea8e

4 touches
1 conflict

0x4dd1db39…a996

0x188d58…ea8e

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

36 conflicts on slot 0x7bd65d3823…13e2df

← previous block·next block →recent activity