← previous blocknext block →recent activity

Analyzing

Block #73,681,288

14 transactions · 14 stateful · 2026-05-10 13:22:22 UTC

Parallelism

64/100

Blocked

36%

Avg conflicts / tx

1.21

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,681,288  ·  14 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

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x529acb6a…fcc6

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x0ac31945…2c72

0x065c9d…c394

4 touches
1 conflict

0xedb848fe…6534

0x34b655…2a6f

2 touches
0 conflicts

0x143dba04…1b98

0x8d66a4…3095

2 touches
0 conflicts

0x7f430e47…4cbd

0x8d66a4…3095

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