← previous blocknext block →recent activity

Analyzing

Block #74,204,310

14 transactions · 10 stateful · 2026-05-12 23:37:01 UTC

Parallelism

79/100

Blocked

30%

Avg conflicts / tx

0.21

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,204,310  ·  14 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xba442629…d236

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xf823e97f…2ee6

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x39aecd8a…6d43

0x065c9d…c394

3 touches
1 conflict

0x10b642bd…b94e

0x065c9d…c394

3 touches
1 conflict

0xb7c34b9e…5921

0x065c9d…c394

2 touches
0 conflicts

0xeaecd67f…36ce

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 0xba442629ad…dbd236

← previous block·next block →recent activity