← previous blocknext block →recent activity

Analyzing

Block #73,273,495

35 transactions · 24 stateful · 2026-05-08 16:04:14 UTC

Parallelism

89/100

Blocked

29%

Avg conflicts / tx

0.31

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,273,495  ·  35 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

0xbd7e37a9…9eb5

0x065c9d…c394

8 touches
6 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xc6417de0…2191

0xc8689a…ee79

4 touches
1 conflict

0xc56ba00d…7700

0x34b655…2a6f

4 touches
1 conflict

0x1319ae2c…7f9a

0x34b655…2a6f

4 touches
1 conflict

0x1b9e654e…0a08

0x34b655…2a6f

4 touches
1 conflict

0x388e001a…7e04

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

6 conflicts on slot 0xbd7e37a9b5…859eb5

← previous block·next block →recent activity