← previous blocknext block →recent activity

Analyzing

Block #73,482,988

27 transactions · 20 stateful · 2026-05-09 15:18:06 UTC

Parallelism

63/100

Blocked

65%

Avg conflicts / tx

1.85

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #73,482,988  ·  27 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x68817ce0…1a37

0xd32edf…ff58

19 touches
45 conflicts

0xa15427f6…d932

0x34b655…2a6f

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0018

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0028

0x1b6862…e19c

4 touches
1 conflict

0x0a6cb118…4ca3

0x1b6862…e19c

4 touches
1 conflict

0xb389d45f…8a4c

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

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

45 conflicts on slot 0x68817ce0ca…fb1a37

← previous block·next block →recent activity