← previous blocknext block →recent activity

Analyzing

Block #74,420,364

16 transactions · 15 stateful · 2026-05-13 23:34:09 UTC

Parallelism

81/100

Blocked

13%

Avg conflicts / tx

0.19

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,420,364  ·  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

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xd09312c2…5ae1

0x065c9d…c394

4 touches
1 conflict

0x22493ab0…7a00

0x065c9d…c394

3 touches
1 conflict

0x6013e375…aca4

0x065c9d…c394

3 touches
1 conflict

0x2e2214a9…fe0d

0x5d823e…89c6

2 touches
0 conflicts

0x3e4b8d9f…b8a7

0x5d823e…89c6

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 0xffe431af56…838faa

← previous block·next block →recent activity