← previous blocknext block →recent activity

Analyzing

Block #73,478,111

20 transactions · 17 stateful · 2026-05-09 14:45:41 UTC

Parallelism

75/100

Blocked

35%

Avg conflicts / tx

0.7

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,478,111  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xf853eb8e…4027

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xd976d098…ae1d

0x34b655…2a6f

6 touches
3 conflicts

0x6eba5e7f…4b52

0x34b655…2a6f

4 touches
1 conflict

0x7cbd466f…1700

0x34b655…2a6f

4 touches
1 conflict

0x849f3e33…c095

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

10 conflicts on slot 0xa91c899f02…fa6ee3

← previous block·next block →recent activity