← previous blocknext block →recent activity

Analyzing

Block #73,046,259

15 transactions · 12 stateful · 2026-05-07 14:52:26 UTC

Parallelism

80/100

Blocked

17%

Avg conflicts / tx

0.2

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,046,259  ·  15 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

0xb0b3056a…0e32

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x49b75562…0cd7

0x065c9d…c394

3 touches
1 conflict

0x0c1639f9…6d51

0x065c9d…c394

3 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

2 touches
0 conflicts

0xd31913b6…6e9a

0x754704…b603

2 touches
0 conflicts

0x01a89030…f786

0x98dc6e…8633

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

1 conflict on slot 0xb0b3056add…ad0e32

← previous block·next block →recent activity