← previous blocknext block →recent activity

Analyzing

Block #74,033,049

12 transactions · 10 stateful · 2026-05-12 04:37:34 UTC

Parallelism

50/100

Blocked

50%

Avg conflicts / tx

1.5

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,033,049  ·  12 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

0x046a928e…0012

0x2a68ba…90c5

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x0fb0ffbc…fe8d

0x065c9d…c394

2 touches
0 conflicts

0x2ce0a3f6…543e

0x065c9d…c394

2 touches
0 conflicts

0x2efab828…b9cf

0x065c9d…c394

2 touches
0 conflicts

0x2fc43a95…ad0e

0x065c9d…c394

2 touches
0 conflicts

0x5be153c8…6d9e

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: 0x2a68ba18…8e90c5

15 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity