← previous blocknext block →recent activity

Analyzing

Block #73,968,927

8 transactions · 7 stateful · 2026-05-11 21:28:23 UTC

Parallelism

75/100

Blocked

14%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,968,927  ·  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

0x9646beaf…8bc3

0x065c9d…c394

4 touches
1 conflict

0x512973f9…9731

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x11dfde03…9d9b

0x065c9d…c394

3 touches
1 conflict

0x47be706b…09d9

0x065c9d…c394

3 touches
1 conflict

0x6f08361d…bda6

0x065c9d…c394

2 touches
0 conflicts

0x7680ee17…7234

0x065c9d…c394

2 touches
0 conflicts

0x93e8dfe6…e63f

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 0x9646beaf22…258bc3

← previous block·next block →recent activity