← previous blocknext block →recent activity

Analyzing

Block #74,216,290

14 transactions · 12 stateful · 2026-05-13 00:56:42 UTC

Parallelism

71/100

Blocked

33%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,216,290  ·  14 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

0x6b319071…a105

0xc8689a…ee79

6 touches
3 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

6 touches
3 conflicts

0x3e4b8d9f…b8a7

0x5d823e…89c6

4 touches
1 conflict

0x50997ada…364d

0x5d823e…89c6

4 touches
1 conflict

0xf0f673fd…37a7

0x5d823e…89c6

4 touches
1 conflict

0xcf3283ba…c9fa

0x065c9d…c394

4 touches
1 conflict

0xf823e97f…2ee6

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

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: 0xc8689a47…62ee79

3 conflicts on slot 0x6b3190712e…20a105

← previous block·next block →recent activity