Block #71,090,072

← previous blocknext block →recent activity

Analyzing

Block #71,090,072

20 transactions · 16 stateful · 2026-04-28 13:32:40 UTC

Parallelism

70/100

Blocked

44%

Avg conflicts / tx

0.8

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,090,072  ·  20 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

0xa431a200…8a21

0xd32edf…ff58

7 touches
6 conflicts

0xfe2bac2b…2cec

0x065c9d…c394

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

6 touches
3 conflicts

0x08d89e5d…bae5

0x065c9d…c394

5 touches
3 conflicts

0xf05b3a49…5092

0x065c9d…c394

4 touches
3 conflicts

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

0xcb45d9d6…cb80

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

6 conflicts on slot 0xa431a2005c…798a21

← previous block·next block →recent activity