← previous blocknext block →recent activity

Analyzing

Block #74,353,289

17 transactions · 14 stateful · 2026-05-13 16:07:42 UTC

Parallelism

82/100

Blocked

29%

Avg conflicts / tx

0.41

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,353,289  ·  17 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

0x6b319071…a105

0xc8689a…ee79

6 touches
3 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

6 touches
3 conflicts

0x50997ada…364d

0x5d823e…89c6

4 touches
2 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x2be283a6…9ed5

0x065c9d…c394

4 touches
1 conflict

0x0175b7a6…1dba

0x5d823e…89c6

4 touches
1 conflict

0x0175b7a6…1dbb

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

3 conflicts on slot 0x6b3190712e…20a105

← previous block·next block →recent activity