← previous blocknext block →recent activity

Analyzing

Block #73,318,861

26 transactions · 18 stateful · 2026-05-08 21:06:08 UTC

Parallelism

73/100

Blocked

39%

Avg conflicts / tx

0.85

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,318,861  ·  26 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x00000000…0002

0xab3526…fa38

14 touches
21 conflicts

0x47c1a8e8…f74a

0x34b655…2a6f

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x8f2a3ce2…4cca

0x065c9d…c394

2 touches
0 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

2 touches
0 conflicts

0x0eac6378…36f4

0x34b655…2a6f

2 touches
0 conflicts

0x33f2d9b1…b689

0x34b655…2a6f

2 touches
0 conflicts

0x8fe0782d…91cf

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: 0xab35264b…1cfa38

21 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity