← previous blocknext block →recent activity

Analyzing

Block #73,324,272

10 transactions · 8 stateful · 2026-05-08 21:42:08 UTC

Parallelism

80/100

Blocked

13%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,324,272  ·  10 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xa91c899f…6ee3

0x34b655…2a6f

4 touches
1 conflict

0x6ddcb186…0578

0x34b655…2a6f

4 touches
1 conflict

0x92339d95…0800

0x0000a8…8888

2 touches
0 conflicts

0x0b28bf77…e53a

0x34b655…2a6f

2 touches
0 conflicts

0x0c5811ce…dfd8

0x34b655…2a6f

2 touches
0 conflicts

0x1319ae2c…7f9a

0x34b655…2a6f

2 touches
0 conflicts

0x2fe4467b…dd70

0x34b655…2a6f

2 touches
0 conflicts

0x32ee90db…decc

0x34b655…2a6f

2 touches
0 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

1 conflict on slot 0xa91c899f02…fa6ee3

← previous block·next block →recent activity