← previous blocknext block →recent activity

Analyzing

Block #73,200,130

11 transactions · 11 stateful · 2026-05-08 07:56:14 UTC

Parallelism

64/100

Blocked

27%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,200,130  ·  11 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x2a354a63…0515

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x8d0b5fc8…b6c7

0x065c9d…c394

2 touches
0 conflicts

0x8e66da19…66b6

0x065c9d…c394

2 touches
0 conflicts

0x0f35726a…f12e

0x21e325…7777

2 touches
0 conflicts

0xbc467e7a…af36

0x21e325…7777

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

6 conflicts on slot 0x2a354a6333…480515

← previous block·next block →recent activity