← previous blocknext block →recent activity

Analyzing

Block #74,475,515

13 transactions · 11 stateful · 2026-05-14 05:41:15 UTC

Parallelism

85/100

Blocked

9%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,475,515  ·  13 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

0x13b1d959…1c28

0x34b655…2a6f

4 touches
1 conflict

0xadac4a86…c2bc

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x0a5f2997…79ac

0x065c9d…c394

2 touches
0 conflicts

0x2ff64df1…cbd1

0x065c9d…c394

2 touches
0 conflicts

0x32b3e556…42aa

0x065c9d…c394

2 touches
0 conflicts

0x4255263d…2887

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: 0x34b6552d…112a6f

1 conflict on slot 0x13b1d959f0…011c28

← previous block·next block →recent activity