← previous blocknext block →recent activity

Analyzing

Block #74,425,033

16 transactions · 16 stateful · 2026-05-14 00:05:17 UTC

Parallelism

81/100

Blocked

25%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,425,033  ·  16 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x9cafc3b6…ee8c

0x000000…012a

4 touches
1 conflict

0x00000000…0036

0x386489…7508

4 touches
1 conflict

0x1a920eda…bfae

0x386489…7508

4 touches
1 conflict

0x59e52fc8…1566

0x754704…b603

4 touches
1 conflict

0xa8669ab5…6af7

0x754704…b603

4 touches
1 conflict

0x00000000…0036

0x784999…1f2d

4 touches
1 conflict

0x2f417c04…a545

0x784999…1f2d

4 touches
1 conflict

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity