← previous blocknext block →recent activity

Analyzing

Block #73,814,511

13 transactions · 12 stateful · 2026-05-11 04:20:07 UTC

Parallelism

77/100

Blocked

33%

Avg conflicts / tx

0.54

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,814,511  ·  13 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x8240d70c…7c3b

0x34b655…2a6f

6 touches
3 conflicts

0x96504a63…52d2

0x8d66a4…3095

4 touches
1 conflict

0x4bfdd5fb…d52b

0x065c9d…c394

4 touches
1 conflict

0x5ba51e87…44ee

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1a7

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1a8

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1ac

0x8d66a4…3095

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity