← previous blocknext block →recent activity

Analyzing

Block #74,389,115

10 transactions · 8 stateful · 2026-05-13 20:06:11 UTC

Parallelism

80/100

Blocked

13%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,389,115  ·  10 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xb0bf63d8…f6d2

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0xbb95558d…66a5

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x16edcffa…031e

0x065c9d…c394

2 touches
0 conflicts

0x2dc6d66e…08f6

0x065c9d…c394

2 touches
0 conflicts

0x3ef2cd7d…6fb2

0x065c9d…c394

2 touches
0 conflicts

0x4db71af9…aa4f

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

1 conflict on slot 0xb0bf63d87b…6df6d2

← previous block·next block →recent activity