← previous blocknext block →recent activity

Analyzing

Block #73,964,672

16 transactions · 11 stateful · 2026-05-11 21:00:03 UTC

Parallelism

69/100

Blocked

45%

Avg conflicts / tx

0.69

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,964,672  ·  16 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

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0xf537eaa0…73c8

0x065c9d…c394

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x1c1a981e…f3da

0xea1b8e…c5ec

2 touches
0 conflicts

0x3572bd92…dd29

0xea1b8e…c5ec

2 touches
0 conflicts

0x3694f0c3…6b8c

0xea1b8e…c5ec

2 touches
0 conflicts

0x36f6824c…700a

0xea1b8e…c5ec

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: 0x2a68ba18…8e90c5

10 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity