← previous blocknext block →recent activity

Analyzing

Block #74,332,717

20 transactions · 15 stateful · 2026-05-13 13:50:57 UTC

Parallelism

80/100

Blocked

27%

Avg conflicts / tx

0.35

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,332,717  ·  20 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x00000000…0002

0xab3526…fa38

8 touches
6 conflicts

0x0175b7a6…1db9

0x5d823e…89c6

4 touches
1 conflict

0x0ef1e663…8f2a

0x5d823e…89c6

4 touches
1 conflict

0x6b319071…a105

0xc8689a…ee79

4 touches
1 conflict

0x52485a48…3166

0x065c9d…c394

2 touches
0 conflicts

0x889e2c9c…4a19

0x065c9d…c394

2 touches
0 conflicts

0x9e9407e5…9124

0x065c9d…c394

2 touches
0 conflicts

0xe2422f8c…00fd

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: 0xab35264b…1cfa38

6 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity