← previous blocknext block →recent activity

Analyzing

Block #73,987,023

13 transactions · 9 stateful · 2026-05-11 23:29:55 UTC

Parallelism

69/100

Blocked

33%

Avg conflicts / tx

0.46

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,987,023  ·  13 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

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x972da85f…50ac

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x764d6335…efe7

0xd32edf…ff58

7 touches
6 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

4 touches
1 conflict

0xd988e3ae…725e

0x3bd359…433a

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x6a44543f…03a4

0x065c9d…c394

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: 0x1b68626d…2de19c

6 conflicts on slot 0x0000000000…000013

← previous block·next block →recent activity