← previous blocknext block →recent activity

Analyzing

Block #73,308,067

16 transactions · 14 stateful · 2026-05-08 19:54:14 UTC

Parallelism

81/100

Blocked

43%

Avg conflicts / tx

0.56

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,308,067  ·  16 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x4882f28c…1ce1

0x065c9d…c394

2 touches
0 conflicts

0x5cfaaedb…d89c

0x065c9d…c394

2 touches
0 conflicts

0xb7d15ec5…175b

0x065c9d…c394

2 touches
0 conflicts

0xbd7e37a9…9eb5

0x065c9d…c394

2 touches
0 conflicts

0xd62ccacf…e24f

0x065c9d…c394

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

3 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity