Block #73,200,395

← previous blocknext block →recent activity

Analyzing

Block #73,200,395

7 transactions · 7 stateful · 2026-05-08 07:58:00 UTC

Parallelism

71/100

Blocked

14%

Avg conflicts / tx

0.29

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,200,395  ·  7 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

0x01fc9fa4…4e1d

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x36086c73…22f6

0x065c9d…c394

3 touches
1 conflict

0x9bc00fcb…ea2a

0x065c9d…c394

3 touches
1 conflict

0x0e50261a…6623

0x065c9d…c394

2 touches
0 conflicts

0x5c1ca38a…261e

0x065c9d…c394

2 touches
0 conflicts

0x8dadd517…7900

0x065c9d…c394

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

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 0x01fc9fa4c7…d64e1d

← previous block·next block →recent activity