← previous blocknext block →recent activity

Analyzing

Block #73,705,514

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

Parallelism

64/100

Blocked

36%

Avg conflicts / tx

0.86

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,705,514  ·  14 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

6 touches
3 conflicts

0x0ac31945…2c72

0x065c9d…c394

6 touches
3 conflicts

0xf10ed50d…a325

0x065c9d…c394

4 touches
1 conflict

0x71f7107b…c5e5

0x065c9d…c394

3 touches
1 conflict

0x68faa0b9…14af

0x368ee5…7ca4

2 touches
0 conflicts

0xcd621226…2df8

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: 0x065c9d28…a9c394

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity