← previous blocknext block →recent activity

Analyzing

Block #74,645,863

14 transactions · 11 stateful · 2026-05-15 00:43:03 UTC

Parallelism

86/100

Blocked

27%

Avg conflicts / tx

0.21

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,645,863  ·  14 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

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x968bdacb…f461

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00bac013…a28c

0x91b81b…6d56

4 touches
1 conflict

0x25b00bf5…3e2e

0xea1b8e…c5ec

4 touches
1 conflict

0xc079cc93…b57b

0xea1b8e…c5ec

4 touches
1 conflict

0x2e52bf33…2824

0x065c9d…c394

3 touches
1 conflict

0x9194f4a3…10b8

0x754704…b603

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 0x5c8c6ab6f0…86dc36

← previous block·next block →recent activity