← previous blocknext block →recent activity

Analyzing

Block #73,697,672

17 transactions · 17 stateful · 2026-05-10 15:12:44 UTC

Parallelism

47/100

Blocked

59%

Avg conflicts / tx

2.29

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,697,672  ·  17 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xf2f76ab3…623e

0x2a68ba…90c5

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

12 touches
15 conflicts

0x0ac31945…2c72

0x065c9d…c394

6 touches
3 conflicts

0x12ee0db9…8df4

0x065c9d…c394

4 touches
1 conflict

0x6d61a5a2…f3fe

0x065c9d…c394

4 touches
1 conflict

0xc1290c27…4cce

0x065c9d…c394

4 touches
1 conflict

0x5b571ba0…f13a

0x368ee5…7ca4

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