← previous blocknext block →recent activity

Analyzing

Block #74,454,821

16 transactions · 11 stateful · 2026-05-14 03:23:36 UTC

Parallelism

75/100

Blocked

27%

Avg conflicts / tx

0.31

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,454,821  ·  16 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

0xe67ad5f2…5bd4

0x065c9d…c394

6 touches
3 conflicts

0x2ec4e5a2…bad9

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x6b319071…a105

0xc8689a…ee79

4 touches
1 conflict

0x0f9a3a01…08e7

0x065c9d…c394

4 touches
1 conflict

0x0175b7a6…1dba

0x5d823e…89c6

4 touches
1 conflict

0x0175b7a6…1dbb

0x5d823e…89c6

4 touches
1 conflict

0x0ef1e663…8f2a

0x5d823e…89c6

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: 0x065c9d28…a9c394

3 conflicts on slot 0xe67ad5f269…0a5bd4

← previous block·next block →recent activity