Block #71,090,128

← previous blocknext block →recent activity

Analyzing

Block #71,090,128

36 transactions · 29 stateful · 2026-04-28 13:33:03 UTC

Parallelism

75/100

Blocked

55%

Avg conflicts / tx

1.25

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #71,090,128  ·  36 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

0xa18bc8b5…0f72

0xd32edf…ff58

15 touches
28 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

8 touches
6 conflicts

0xaccba919…a9a2

0x065c9d…c394

7 touches
6 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

0xe89e1a22…ce49

0x8d66a4…3095

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

28 conflicts on slot 0xa18bc8b5ab…710f72

← previous block·next block →recent activity