← previous blocknext block →recent activity

Analyzing

Block #73,297,662

11 transactions · 8 stateful · 2026-05-08 18:45:00 UTC

Parallelism

82/100

Blocked

13%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,297,662  ·  11 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x6f08361d…bda6

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x30a6b0d6…d52a

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x0e6a4aaf…aca5

0x065c9d…c394

2 touches
0 conflicts

0x13b3098b…b95d

0x065c9d…c394

2 touches
0 conflicts

0x2cd9c476…3ce7

0x065c9d…c394

2 touches
0 conflicts

0xc7e365cf…9130

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

1 conflict on slot 0x6f08361da9…89bda6

← previous block·next block →recent activity