← previous blocknext block →recent activity

Analyzing

Block #73,748,958

18 transactions · 17 stateful · 2026-05-10 20:58:53 UTC

Parallelism

56/100

Blocked

47%

Avg conflicts / tx

1.5

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,748,958  ·  18 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x7f81fb82…633e

0x065c9d…c394

8 touches
6 conflicts

0xb159af88…a9e7

0x065c9d…c394

4 touches
1 conflict

0x01a89030…f786

0x98dc6e…8633

2 touches
0 conflicts

0x0fc41e7b…6831

0x98dc6e…8633

2 touches
0 conflicts

0x5b571ba0…f13a

0x98dc6e…8633

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

15 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity