← previous blocknext block →recent activity

Analyzing

Block #73,343,402

11 transactions · 9 stateful · 2026-05-08 23:49:20 UTC

Parallelism

82/100

Blocked

22%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,343,402  ·  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

0xbd7e37a9…9eb5

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x0b390c61…dc07

0x065c9d…c394

4 touches
1 conflict

0x0eac6378…36f4

0x34b655…2a6f

2 touches
0 conflicts

0x25f8183e…b2d2

0x34b655…2a6f

2 touches
0 conflicts

0x33f2d9b1…b689

0x34b655…2a6f

2 touches
0 conflicts

0x42fc886d…c90d

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

1 conflict on slot 0xbd7e37a9b5…859eb5

← previous block·next block →recent activity