← previous blocknext block →recent activity

Analyzing

Block #73,187,421

8 transactions · 6 stateful · 2026-05-08 06:31:39 UTC

Parallelism

75/100

Blocked

17%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,187,421  ·  8 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

0x583e8d12…01e5

0x065c9d…c394

4 touches
1 conflict

0x68146685…0fe5

0x065c9d…c394

3 touches
1 conflict

0xb95f8375…8d74

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x04bc1ae0…09aa

0x065c9d…c394

2 touches
0 conflicts

0x2a354a63…0515

0x065c9d…c394

2 touches
0 conflicts

0x2fa001c6…3386

0x065c9d…c394

2 touches
0 conflicts

0xa463686a…fc67

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 0x583e8d12ff…9a01e5

← previous block·next block →recent activity