← previous blocknext block →recent activity

Analyzing

Block #72,856,159

22 transactions · 20 stateful · 2026-05-06 17:47:10 UTC

Parallelism

73/100

Blocked

30%

Avg conflicts / tx

0.68

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,856,159  ·  22 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

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0xce7bfe5e…5e58

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x73dd9beb…a6a9

0x065c9d…c394

4 touches
1 conflict

0x9759e083…7413

0x065c9d…c394

4 touches
1 conflict

0xf853eb8e…401e

0x34b655…2a6f

2 touches
0 conflicts

0x8956cb26…42f7

0x44b60b…f711

2 touches
0 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

10 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity