← previous blocknext block →recent activity

Analyzing

Block #73,653,576

14 transactions · 14 stateful · 2026-05-10 10:15:16 UTC

Parallelism

36/100

Blocked

64%

Avg conflicts / tx

2.43

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,653,576  ·  14 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

0x00000000…003d

0x065c9d…c394

12 touches
15 conflicts

0x046a928e…0012

0x2a68ba…90c5

12 touches
15 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

10 touches
10 conflicts

0x7f81fb82…633e

0x065c9d…c394

10 touches
10 conflicts

0xb159af88…a9e7

0x065c9d…c394

6 touches
3 conflicts

0x5724876e…6ac4

0x065c9d…c394

2 touches
0 conflicts

0x5bcf269a…c2ff

0x065c9d…c394

2 touches
0 conflicts

0x6c658403…736b

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

15 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity