← previous blocknext block →recent activity

Analyzing

Block #73,273,647

17 transactions · 14 stateful · 2026-05-08 16:05:14 UTC

Parallelism

53/100

Blocked

57%

Avg conflicts / tx

1.71

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,273,647  ·  17 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x3c9a602e…cfd8

0xd32edf…ff58

15 touches
28 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002c

0x1b6862…e19c

4 touches
1 conflict

0x872e51c8…ae29

0x1b6862…e19c

4 touches
1 conflict

0x038aa895…2f47

0x34b655…2a6f

4 touches
1 conflict

0x388e001a…7e04

0x34b655…2a6f

4 touches
1 conflict

0x6eba5e7f…4b52

0x34b655…2a6f

4 touches
1 conflict

0x9776ae1b…1a92

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

28 conflicts on slot 0x3c9a602eef…43cfd8

← previous block·next block →recent activity