← previous blocknext block →recent activity

Analyzing

Block #73,343,731

18 transactions · 15 stateful · 2026-05-08 23:51:31 UTC

Parallelism

72/100

Blocked

33%

Avg conflicts / tx

0.61

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,343,731  ·  18 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xd8dd8fb2…4689

0xd32edf…ff58

9 touches
10 conflicts

0xbdff944d…447e

0x2a68ba…90c5

4 touches
1 conflict

0x7d3863bd…3b17

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x09521845…2018

0x065c9d…c394

2 touches
0 conflicts

0x38586368…28d4

0x065c9d…c394

2 touches
0 conflicts

0x5b74909a…9f51

0x065c9d…c394

2 touches
0 conflicts

0x6f08361d…bda6

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: 0xd32edf66…9fff58

10 conflicts on slot 0xd8dd8fb2c7…704689

← previous block·next block →recent activity