← previous blocknext block →recent activity

Analyzing

Block #73,035,153

45 transactions · 25 stateful · 2026-05-07 13:38:29 UTC

Parallelism

80/100

Blocked

52%

Avg conflicts / tx

1.02

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,035,153  ·  45 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x150f1789…801f

0xd32edf…ff58

17 touches
36 conflicts

0xe09eda07…8dda

0x2a68ba…90c5

8 touches
6 conflicts

0xbd7e37a9…9eb5

0x065c9d…c394

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001f

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002f

0x1b6862…e19c

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

36 conflicts on slot 0x150f17898a…51801f

← previous block·next block →recent activity