← previous blocknext block →recent activity

Analyzing

Block #73,643,144

20 transactions · 11 stateful · 2026-05-10 09:05:01 UTC

Parallelism

85/100

Blocked

27%

Avg conflicts / tx

0.2

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,643,144  ·  20 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

0x8a2657f5…e008

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xf882d8d1…c9c7

0x34b655…2a6f

4 touches
1 conflict

0x438cf5f6…f077

0x2a68ba…90c5

4 touches
1 conflict

0x02b51749…1541

0x34b655…2a6f

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xa590e52f…fdfd

0x0555e3…2b9c

2 touches
0 conflicts

0x44f35905…7817

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: 0x34b6552d…112a6f

3 conflicts on slot 0x8a2657f5c3…4ce008

← previous block·next block →recent activity