← previous blocknext block →recent activity

Analyzing

Block #73,652,137

20 transactions · 20 stateful · 2026-05-10 10:05:32 UTC

Parallelism

60/100

Blocked

60%

Avg conflicts / tx

2.05

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,652,137  ·  20 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

12 touches
15 conflicts

0x7f81fb82…633e

0x065c9d…c394

12 touches
15 conflicts

0xb159af88…a9e7

0x065c9d…c394

12 touches
15 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

12 touches
15 conflicts

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0xc6417de0…2191

0xc8689a…ee79

4 touches
1 conflict

0xa91c899f…6ee3

0x34b655…2a6f

4 touches
1 conflict

0xf7ec4cb6…8774

0x34b655…2a6f

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

15 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity