← previous blocknext block →recent activity

Analyzing

Block #73,502,920

6 transactions · 5 stateful · 2026-05-09 17:30:52 UTC

Parallelism

67/100

Blocked

20%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,502,920  ·  6 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

0x22e295f5…1bef

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x06e89564…650d

0x10aeaf…5417

2 touches
0 conflicts

0x0dbf9688…c6cf

0x10aeaf…5417

2 touches
0 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

2 touches
0 conflicts

0x01e7b865…6e6e

0x188d58…ea8e

2 touches
0 conflicts

0x36cd3056…b5d4

0x188d58…ea8e

2 touches
0 conflicts

0x36cd3056…b5d6

0x188d58…ea8e

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 0x22e295f5d8…ac1bef

← previous block·next block →recent activity