← previous blocknext block →recent activity

Analyzing

Block #71,445,789

19 transactions · 18 stateful · 2026-04-30 05:01:56 UTC

Parallelism

68/100

Blocked

61%

Avg conflicts / tx

1.26

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #71,445,789  ·  19 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

0x892daf6e…48d8

0x065c9d…c394

8 touches
8 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x451e482b…7e7d

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x5f77d607…2c84

0x065c9d…c394

6 touches
3 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

6 touches
3 conflicts

0x00000000…0000

0x63e48b…53f2

6 touches
3 conflicts

0x00000000…0002

0x63e48b…53f2

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: 0x065c9d28…a9c394

8 conflicts on slot 0x892daf6e5d…6d48d8

← previous block·next block →recent activity