← previous blocknext block →recent activity

Analyzing

Block #73,161,922

15 transactions · 14 stateful · 2026-05-08 03:41:41 UTC

Parallelism

67/100

Blocked

29%

Avg conflicts / tx

0.6

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,161,922  ·  15 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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0xce7bfe5e…5e58

0x065c9d…c394

4 touches
1 conflict

0x037849a8…fa88

0x34b655…2a6f

2 touches
0 conflicts

0x4fe4d51f…835a

0x34b655…2a6f

2 touches
0 conflicts

0x87be01b5…e34e

0x34b655…2a6f

2 touches
0 conflicts

0xc824469a…641d

0x34b655…2a6f

2 touches
0 conflicts

0xc824469a…641f

0x34b655…2a6f

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 0x0000000000…00003d

← previous block·next block →recent activity