← previous blocknext block →recent activity

Analyzing

Block #73,035,154

31 transactions · 22 stateful · 2026-05-07 13:38:30 UTC

Parallelism

81/100

Blocked

41%

Avg conflicts / tx

0.61

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,035,154  ·  31 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xf2a1c9b7…b9d6

0xd32edf…ff58

11 touches
15 conflicts

0x1eb0fab5…3517

0x34b655…2a6f

4 touches
1 conflict

0x41c1f3e5…c9b1

0x34b655…2a6f

4 touches
1 conflict

0x85a88798…f85e

0x34b655…2a6f

4 touches
1 conflict

0xd1efe2a0…3c60

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xdaca243a…f9de

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1539

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

15 conflicts on slot 0xf2a1c9b778…6fb9d6

← previous block·next block →recent activity