Block #73,201,640

← previous blocknext block →recent activity

Analyzing

Block #73,201,640

20 transactions · 16 stateful · 2026-05-08 08:06:17 UTC

Parallelism

70/100

Blocked

56%

Avg conflicts / tx

1.1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,201,640  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x046a928e…0012

0x2a68ba…90c5

12 touches
15 conflicts

0x7f189cf6…afab

0x065c9d…c394

8 touches
6 conflicts

0xc35ffda5…10e2

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x17c24c1f…6752

0x065c9d…c394

2 touches
0 conflicts

0x2c104d65…e348

0x065c9d…c394

2 touches
0 conflicts

0x8138e377…0676

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: 0x2a68ba18…8e90c5

15 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity