← previous blocknext block →recent activity

Analyzing

Block #73,343,436

20 transactions · 17 stateful · 2026-05-08 23:49:34 UTC

Parallelism

80/100

Blocked

18%

Avg conflicts / tx

0.3

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x6f08361d…bda6

0x065c9d…c394

8 touches
6 conflicts

0xe94e77ab…f017

0xaba216…a862

4 touches
1 conflict

0xd821ae10…fe17

0xc8689a…ee79

4 touches
1 conflict

0x3e4b8d9f…b8a7

0xaba216…a862

4 touches
1 conflict

0xe7535190…5a0f

0xaba216…a862

4 touches
1 conflict

0xf537eaa0…73c8

0x065c9d…c394

4 touches
1 conflict

0x8d0dfe2c…3345

0x2a68ba…90c5

4 touches
1 conflict

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