← previous blocknext block →recent activity

Analyzing

Block #74,183,340

12 transactions · 11 stateful · 2026-05-12 21:17:35 UTC

Parallelism

75/100

Blocked

18%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,183,340  ·  12 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

0xf823e97f…2ee6

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x0146366a…02dd

0x065c9d…c394

2 touches
0 conflicts

0x2356fe6d…bab4

0x065c9d…c394

2 touches
0 conflicts

0x371cd93a…cc6e

0x065c9d…c394

2 touches
0 conflicts

0x64d94cc1…f81e

0x065c9d…c394

2 touches
0 conflicts

0x90d2c8a1…d2bc

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

3 conflicts on slot 0xf823e97fa0…262ee6

← previous block·next block →recent activity