← previous blocknext block →recent activity

Analyzing

Block #73,046,498

30 transactions · 22 stateful · 2026-05-07 14:54:02 UTC

Parallelism

70/100

Blocked

55%

Avg conflicts / tx

1.47

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,046,498  ·  30 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

0xd98b3c10…67b8

0x34b655…2a6f

16 touches
28 conflicts

0x388e001a…7e04

0x34b655…2a6f

10 touches
10 conflicts

0x578e7f66…1b56

0x34b655…2a6f

8 touches
6 conflicts

0xf853eb8e…4027

0x34b655…2a6f

8 touches
6 conflicts

0x602ff3d4…3ebd

0x34b655…2a6f

8 touches
6 conflicts

0x8a85cf3d…2868

0x34b655…2a6f

6 touches
3 conflicts

0xa7a586ac…c700

0x34b655…2a6f

6 touches
3 conflicts

0x908d4442…2c4b

0x34b655…2a6f

6 touches
3 conflicts

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: 0x34b6552d…112a6f

28 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity