← previous blocknext block →recent activity

Analyzing

Block #73,653,195

13 transactions · 12 stateful · 2026-05-10 10:12:39 UTC

Parallelism

46/100

Blocked

67%

Avg conflicts / tx

2.31

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,653,195  ·  13 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x0ac31945…2c72

0x065c9d…c394

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

12 touches
15 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

12 touches
15 conflicts

0xe46c960a…6de1

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x13e89f47…53e9

0x065c9d…c394

3 touches
1 conflict

0x0be8b3d8…ac1a

0x065c9d…c394

3 touches
1 conflict

0xd8484db3…b251

0x065c9d…c394

3 touches
1 conflict

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

15 conflicts on slot 0x0ac3194537…8f2c72

← previous block·next block →recent activity