← previous blocknext block →recent activity

Analyzing

Block #73,201,014

10 transactions · 9 stateful · 2026-05-08 08:02:07 UTC

Parallelism

70/100

Blocked

22%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,201,014  ·  10 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…003d

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x92339d95…0800

0x0000a8…8888

2 touches
0 conflicts

0x2a354a63…0515

0x065c9d…c394

2 touches
0 conflicts

0x37af957e…0a1d

0x065c9d…c394

2 touches
0 conflicts

0x827a6b50…e869

0x065c9d…c394

2 touches
0 conflicts

0xa9157af9…1b25

0x065c9d…c394

2 touches
0 conflicts

0xabf63b31…8295

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: 0x065c9d28…a9c394

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity