← previous blocknext block →recent activity

Analyzing

Block #73,657,926

14 transactions · 13 stateful · 2026-05-10 10:44:38 UTC

Parallelism

57/100

Blocked

46%

Avg conflicts / tx

1.14

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,657,926  ·  14 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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0xb159af88…a9e7

0x065c9d…c394

4 touches
1 conflict

0x0848ffbe…ac05

0x065c9d…c394

3 touches
1 conflict

0x081c1c43…e06d

0x065c9d…c394

3 touches
1 conflict

0x95b72589…7dde

0x065c9d…c394

2 touches
0 conflicts

0xb58271e9…4a7b

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity