← previous blocknext block →recent activity

Analyzing

Block #72,283,089

17 transactions · 12 stateful · 2026-05-04 02:07:33 UTC

Parallelism

76/100

Blocked

42%

Avg conflicts / tx

0.53

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,283,089  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x1a6828a0…19c5

0xd32edf…ff58

7 touches
6 conflicts

0x8a35acfb…d1ac

0x8d66a4…3095

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0xe783dfa4…5493

0x1b6862…e19c

4 touches
1 conflict

0x8d9d7967…d020

0x065c9d…c394

4 touches
1 conflict

0x96504a63…52d2

0x8d66a4…3095

4 touches
1 conflict

0xcc6521c1…c892

0x8d66a4…3095

4 touches
1 conflict

0x74e71984…ae90

0x2a68ba…90c5

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 0x1a6828a0c4…2d19c5

← previous block·next block →recent activity